← previous blocknext block →recent activity

Analyzing

Block #73,041,798

39 transactions · 31 stateful · 2026-05-07 14:22:42 UTC

Parallelism

80/100

Blocked

58%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,041,798  ·  39 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa0b0925e…d4bb

0xd32edf…ff58

15 touches
28 conflicts

0x7f189cf6…afab

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf4730a2d…3538

0x34b655…2a6f

8 touches
6 conflicts

0x0520da1d…c88e

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

6 touches
3 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0xd32edf66…9fff58

28 conflicts on slot 0xa0b0925eaa…13d4bb

← previous block·next block →recent activity