← previous blocknext block →recent activity
Analyzing
Block #85,201,106
9 transactions · 8 stateful · 2026-07-02 22:21:49 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,201,106 · 9 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
1w02w16w2
- 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
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x9932ca22…d3f1
0x065c9d…c394
3 touches
1 conflict
0x81133657…6614
0x065c9d…c394
2 touches
0 conflicts
0xb10ce2ba…8f86
0x065c9d…c394
2 touches
0 conflicts
0xf88c36ad…e6dd
0x065c9d…c394
2 touches
0 conflicts
0xfc04ef87…c151
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