← previous blocknext block →recent activity
Analyzing
Block #85,680,233
16 transactions · 13 stateful · 2026-07-05 03:32:25 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,680,233 · 16 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
1w03w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb68e226d…c054
0xa6afd3…d132
4 touches
1 conflict
0xb704214a…5aa0
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x131a2e…0da9
2 touches
0 conflicts
0x5540f956…69e8
0x131a2e…0da9
2 touches
0 conflicts
0x9ff176a9…152e
0x131a2e…0da9
2 touches
0 conflicts
0xc7dfe3f5…17d5
0x131a2e…0da9
2 touches
0 conflicts
0xc7dfe3f5…17d6
0x131a2e…0da9
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity