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