← previous blocknext block →recent activity
Analyzing
Block #85,518,614
20 transactions · 16 stateful · 2026-07-04 09:36:20 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,518,614 · 20 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
1w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x012c7ec1…1707
0x065c9d…c394
2 touches
0 conflicts
0x0a592216…c8fb
0x065c9d…c394
2 touches
0 conflicts
0x13861502…0915
0x065c9d…c394
2 touches
0 conflicts
0x62e66978…fc53
0x065c9d…c394
2 touches
0 conflicts
0x64b06001…e222
0x065c9d…c394
2 touches
0 conflicts
0xbb32dddd…a2c5
0x065c9d…c394
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