← previous blocknext block →recent activity
Analyzing
Block #85,506,713
10 transactions · 9 stateful · 2026-07-04 08:17:09 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,506,713 · 10 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3181bd2d…cf15
0xa6afd3…d132
4 touches
1 conflict
0xb795deba…804e
0xa6afd3…d132
3 touches
1 conflict
0xca39f670…ec76
0xa6afd3…d132
3 touches
1 conflict
0x503b3a72…f6df
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x87764a18…fac3
0x34b655…2a6f
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 0xb68e226d12…aac054
Audit this contract →
← previous block·next block →recent activity