← previous blocknext block →recent activity
Analyzing
Block #72,208,932
21 transactions · 17 stateful · 2026-05-03 17:49:12 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,208,932 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w09w110w211w212w315w117w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ab
0x8d66a4…3095
8 touches
6 conflicts
0xa02838a3…bc54
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x414e9446…4b59
0x34b655…2a6f
6 touches
3 conflicts
0xa8bd52b5…862e
0x34b655…2a6f
6 touches
3 conflicts
0xe89e1a22…ce49
0x8d66a4…3095
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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: 0x8d66a43f…113095
6 conflicts on slot 0x8a35acfbc1…6bd1ab
Audit this contract →
← previous block·next block →recent activity