← previous blocknext block →recent activity
Analyzing
Block #95,592,443
14 transactions · 14 stateful · 2026-08-13 09:13:18 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,592,443 · 14 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
1w02w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc6b1d981…1be2
0xa6afd3…d132
4 touches
1 conflict
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0x6d12cba8…e4ff
0xa6afd3…d132
3 touches
1 conflict
0xb4e082fd…9264
0xa6afd3…d132
3 touches
1 conflict
0xc4d0d663…a923
0xa6afd3…d132
3 touches
1 conflict
0x59ed86dc…8b49
0xa6afd3…d132
3 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity