← previous blocknext block →recent activity
Analyzing
Block #96,084,861
20 transactions · 18 stateful · 2026-08-15 02:31:35 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,084,861 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w29w212w314w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c3b1720…677d
0x968279…9342
8 touches
6 conflicts
0x521a5982…a82a
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x51b0e0df…3918
0x968279…9342
8 touches
6 conflicts
0x51b0e0df…3919
0x968279…9342
8 touches
6 conflicts
0x51b0e0df…391b
0x968279…9342
8 touches
6 conflicts
0x6c3b1720…6776
0x968279…9342
8 touches
6 conflicts
0x6c3b1720…6777
0x968279…9342
8 touches
6 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
6 conflicts on slot 0x6c3b17202d…71677d
Audit this contract →
← previous block·next block →recent activity