← previous blocknext block →recent activity
Analyzing
Block #86,705,534
14 transactions · 14 stateful · 2026-07-09 21:39:40 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,705,534 · 14 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
1w05w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdf15e2bf…d7a9
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0xfa3848f5…98ee
0x34b655…2a6f
4 touches
1 conflict
0xfd67b4dc…033a
0x34b655…2a6f
4 touches
1 conflict
0x00a4f539…8b4a
0x34b655…2a6f
4 touches
1 conflict
0x328829c6…1739
0x34b655…2a6f
4 touches
1 conflict
0x43c2fa32…4d82
0x34b655…2a6f
4 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity