← previous blocknext block →recent activity
Analyzing
Block #85,629,262
10 transactions · 10 stateful · 2026-07-04 21:53:08 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,629,262 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5cc231f5…f1cd
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6a9d
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6a9f
0x69df8a…6292
4 touches
1 conflict
0xe2263bea…6aa0
0x69df8a…6292
4 touches
1 conflict
0xea8e47b0…abfe
0x69df8a…6292
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity