← previous blocknext block →recent activity
Analyzing
Block #85,182,612
16 transactions · 16 stateful · 2026-07-02 20:18:43 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,182,612 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7b4cadeb…b103
0x065c9d…c394
4 touches
1 conflict
0xd6fc27ae…d42a
0x065c9d…c394
3 touches
1 conflict
0x1684b22b…d996
0x065c9d…c394
3 touches
1 conflict
0x4abd2b8d…dfaf
0x065c9d…c394
3 touches
1 conflict
0x026527e9…6994
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity