← previous blocknext block →recent activity
Analyzing
Block #96,030,201
12 transactions · 11 stateful · 2026-08-14 21:56:38 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,030,201 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab34c8a2…ed49
0x968279…9342
6 touches
3 conflicts
0x5d195a79…963e
0x968279…9342
6 touches
3 conflicts
0x5d195a79…9640
0x968279…9342
6 touches
3 conflicts
0xab34c8a2…ed43
0x968279…9342
6 touches
3 conflicts
0xab34c8a2…ed44
0x968279…9342
6 touches
3 conflicts
0xab34c8a2…ed47
0x968279…9342
6 touches
3 conflicts
0xab34c8a2…ed48
0x968279…9342
6 touches
3 conflicts
0x811e9179…ea02
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: 0x96827978…f09342
3 conflicts on slot 0xab34c8a261…55ed49
Audit this contract →
← previous block·next block →recent activity