← previous blocknext block →recent activity
Analyzing
Block #85,761,788
16 transactions · 12 stateful · 2026-07-05 12:36:47 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,761,788 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc87a5a7b…4a1b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xbbe555fd…8e2a
0x065c9d…c394
3 touches
1 conflict
0xa3b7086d…1050
0x065c9d…c394
3 touches
1 conflict
0x131cb7c9…5da2
0x065c9d…c394
3 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
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 0xc87a5a7bda…e94a1b
Audit this contract →
← previous block·next block →recent activity