← previous blocknext block →recent activity
Analyzing
Block #85,810,613
10 transactions · 8 stateful · 2026-07-05 18:02:03 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,810,613 · 10 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
1w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xf1978be7…d3c4
0x065c9d…c394
4 touches
1 conflict
0xf602d604…6be4
0x065c9d…c394
3 touches
1 conflict
0xe24ef46d…aa2c
0x065c9d…c394
3 touches
1 conflict
0x0e9f111c…0869
0x34b655…2a6f
2 touches
0 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
2 touches
0 conflicts
0x1fe92c2a…cbb1
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity