← previous blocknext block →recent activity
Analyzing
Block #96,450,069
17 transactions · 14 stateful · 2026-08-16 09:08:26 UTC
Parallelism
53/100
Blocked
57%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,450,069 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w110w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae6b6f0b…607c
0x968279…9342
16 touches
28 conflicts
0x521a5982…a82a
0x754704…b603
16 touches
28 conflicts
0x00000000…0006
0x968279…9342
16 touches
28 conflicts
0x4a1de7fe…95cf
0x968279…9342
16 touches
28 conflicts
0x4a1de7fe…95d0
0x968279…9342
16 touches
28 conflicts
0x4a1de7fe…95d3
0x968279…9342
16 touches
28 conflicts
0x4a1de7fe…95d4
0x968279…9342
16 touches
28 conflicts
0x4a1de7fe…95d6
0x968279…9342
16 touches
28 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
28 conflicts on slot 0xae6b6f0bc6…c8607c
Audit this contract →
← previous block·next block →recent activity