← previous blocknext block →recent activity
Analyzing
Block #85,173,332
14 transactions · 11 stateful · 2026-07-02 19:16:49 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,173,332 · 14 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
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9d9cf253…0748
0x065c9d…c394
4 touches
1 conflict
0xab944820…0ee8
0x065c9d…c394
3 touches
1 conflict
0xbbcdf8d1…1c0f
0x065c9d…c394
3 touches
1 conflict
0x23d6464e…d669
0xd32edf…ff58
3 touches
1 conflict
0x57e5307c…8834
0x065c9d…c394
2 touches
0 conflicts
0x5a900395…4eb6
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
1 conflict on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity