← previous blocknext block →recent activity
Analyzing
Block #96,450,079
17 transactions · 13 stateful · 2026-08-16 09:08:29 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,450,079 · 17 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
3w04w15w07w19w010w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae6b6f0b…607c
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x4a1de7fe…95cf
0x968279…9342
6 touches
3 conflicts
0x4a1de7fe…95d0
0x968279…9342
6 touches
3 conflicts
0x4a1de7fe…95d3
0x968279…9342
6 touches
3 conflicts
0x4a1de7fe…95d4
0x968279…9342
6 touches
3 conflicts
0x4a1de7fe…95d6
0x968279…9342
6 touches
3 conflicts
0xae6b6f0b…6079
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 0xae6b6f0bc6…c8607c
Audit this contract →
← previous block·next block →recent activity