← previous blocknext block →recent activity
Analyzing
Block #73,036,672
22 transactions · 16 stateful · 2026-05-07 13:48:36 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,036,672 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w39w011w113w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
8 touches
6 conflicts
0x00000000…000b
0x6ca43f…c331
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6ca43f…c331
4 touches
1 conflict
0x5b3dfef8…a676
0x6ca43f…c331
4 touches
1 conflict
0x4e5ebbf7…ae70
0xc8689a…ee79
4 touches
1 conflict
0x594c0946…b14c
0x065c9d…c394
4 touches
1 conflict
0xcdf15db4…ab6a
0x065c9d…c394
4 touches
1 conflict
0x5d70606a…1d53
0x34b655…2a6f
4 touches
1 conflict
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: 0xd574cae5…037ab1
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity