← previous blocknext block →recent activity
Analyzing
Block #96,114,564
11 transactions · 11 stateful · 2026-08-15 05:00:58 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,114,564 · 11 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
1w02w15w06w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba6c9e6…2a83
0x968279…9342
6 touches
3 conflicts
0xeda8a448…5ca3
0x968279…9342
6 touches
3 conflicts
0xeda8a448…5ca5
0x968279…9342
6 touches
3 conflicts
0x3ba6c9e6…2a7d
0x968279…9342
6 touches
3 conflicts
0x3ba6c9e6…2a7e
0x968279…9342
6 touches
3 conflicts
0x3ba6c9e6…2a81
0x968279…9342
6 touches
3 conflicts
0x3ba6c9e6…2a82
0x968279…9342
6 touches
3 conflicts
0xeda8a448…5ca2
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 0x3ba6c9e682…d82a83
Audit this contract →
← previous block·next block →recent activity