← previous blocknext block →recent activity
Analyzing
Block #96,443,366
11 transactions · 10 stateful · 2026-08-16 08:34:44 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,443,366 · 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
1w02w03w16w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2f59d24…00f9
0x968279…9342
6 touches
3 conflicts
0x135f48c1…3430
0x968279…9342
6 touches
3 conflicts
0x135f48c1…3431
0x968279…9342
6 touches
3 conflicts
0x135f48c1…3434
0x968279…9342
6 touches
3 conflicts
0x135f48c1…3435
0x968279…9342
6 touches
3 conflicts
0x135f48c1…3436
0x968279…9342
6 touches
3 conflicts
0xc2f59d24…00f6
0x968279…9342
6 touches
3 conflicts
0xc2f59d24…00f7
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 0xc2f59d245d…1800f9
Audit this contract →
← previous block·next block →recent activity