← previous blocknext block →recent activity
Analyzing
Block #96,602,211
11 transactions · 11 stateful · 2026-08-16 21:53:59 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,602,211 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x283478b0…8f45
0xa6afd3…d132
4 touches
1 conflict
0xf9f9f64b…242d
0xa6afd3…d132
3 touches
1 conflict
0x8f032c88…1d64
0xa6afd3…d132
3 touches
1 conflict
0x83e15f57…c6d9
0xa6afd3…d132
3 touches
1 conflict
0x08f81fb5…9585
0xa6afd3…d132
3 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity