← previous blocknext block →recent activity
Analyzing
Block #85,920,233
18 transactions · 14 stateful · 2026-07-06 06:12:07 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,920,233 · 18 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
5w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaea738f9…68d3
0x065c9d…c394
4 touches
1 conflict
0xb33ff823…1188
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1f610c79…05cb
0x065c9d…c394
3 touches
1 conflict
0x42faeee9…1979
0x065c9d…c394
3 touches
1 conflict
0x9d0208d3…bd8a
0x065c9d…c394
3 touches
1 conflict
0x0f21840f…6cde
0x34b655…2a6f
2 touches
0 conflicts
0x1e7d4e80…68b4
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-MON/USDC
1 conflict on slot 0xaea738f907…8f68d3
Audit this contract →
← previous block·next block →recent activity