← previous blocknext block →recent activity
Analyzing
Block #85,630,625
11 transactions · 9 stateful · 2026-07-04 22:02:13 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,630,625 · 11 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x03fed1d3…f1e9
0x065c9d…c394
4 touches
1 conflict
0xa9c379f1…1736
0x065c9d…c394
3 touches
1 conflict
0xbf996573…9a6e
0x065c9d…c394
3 touches
1 conflict
0xc8295250…0e15
0x065c9d…c394
3 touches
1 conflict
0x62068bf6…8bfb
0x065c9d…c394
3 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x06e40499…165e
0x69df8a…6292
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity