← previous blocknext block →recent activity
Analyzing
Block #85,908,745
16 transactions · 9 stateful · 2026-07-06 04:55:38 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,908,745 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x004c636b…b1ef
0x065c9d…c394
3 touches
1 conflict
0xda673413…4ab8
0x065c9d…c394
3 touches
1 conflict
0x1e5d2f73…c616
0x6657d1…8ccc
2 touches
0 conflicts
0x41004a9f…d00a
0x6657d1…8ccc
2 touches
0 conflicts
0x429fd3db…6709
0x6657d1…8ccc
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-MON/USDC
1 conflict on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity