← previous blocknext block →recent activity
Analyzing
Block #96,508,991
15 transactions · 13 stateful · 2026-08-16 14:05:08 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,508,991 · 15 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
7w08w19w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec2eb737…cae7
0x968279…9342
6 touches
3 conflicts
0x1b7076ea…6cdb
0x968279…9342
6 touches
3 conflicts
0x1b7076ea…6cdc
0x968279…9342
6 touches
3 conflicts
0x1b7076ea…6cde
0x968279…9342
6 touches
3 conflicts
0xec2eb737…cae0
0x968279…9342
6 touches
3 conflicts
0xec2eb737…cae1
0x968279…9342
6 touches
3 conflicts
0xec2eb737…cae4
0x968279…9342
6 touches
3 conflicts
0xec2eb737…cae5
0x968279…9342
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 0xec2eb73702…06cae7
Audit this contract →
← previous block·next block →recent activity