← previous blocknext block →recent activity
Analyzing
Block #72,232,929
8 transactions · 7 stateful · 2026-05-03 20:30:28 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,232,929 · 8 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
2w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaa0d0542…d8ec
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x1179284b…db76
0x34b655…2a6f
4 touches
1 conflict
0x23951077…539b
0x34b655…2a6f
4 touches
1 conflict
0x908d4442…2c4b
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
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: Perpl
3 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity