← previous blocknext block →recent activity
Analyzing
Block #85,624,607
10 transactions · 9 stateful · 2026-07-04 21:22:07 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,624,607 · 10 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e465d19…4e23
0x065c9d…c394
4 touches
1 conflict
0x8a4006ac…de6f
0x065c9d…c394
3 touches
1 conflict
0x1c47b556…5237
0x065c9d…c394
3 touches
1 conflict
0x39b96d2f…17cc
0x065c9d…c394
3 touches
1 conflict
0xbcee8ad2…ed16
0x4c02af…0ac7
2 touches
0 conflicts
0x00000000…0000
0xae3e24…7d91
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity