← previous blocknext block →recent activity
Analyzing
Block #86,363,450
17 transactions · 17 stateful · 2026-07-08 07:31:00 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,363,450 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w39w012w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
6 touches
3 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
6 touches
3 conflicts
0xe85a3d2b…c4df
0xd32edf…ff58
5 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
4 touches
1 conflict
0x36c9c398…b894
0xa6afd3…d132
4 touches
1 conflict
0x130163f9…ffb6
0xa6afd3…d132
3 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity