← previous blocknext block →recent activity
Analyzing
Block #85,756,397
11 transactions · 10 stateful · 2026-07-05 12:00:55 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,756,397 · 11 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
6w07w19w2
- 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
0x5497531e…4d79
0x065c9d…c394
4 touches
1 conflict
0x48c59513…115f
0x065c9d…c394
3 touches
1 conflict
0x84f60c1e…cd54
0x065c9d…c394
3 touches
1 conflict
0x5d14e0ca…b081
0x065c9d…c394
3 touches
1 conflict
0x645b31e4…d52e
0x065c9d…c394
3 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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