← previous blocknext block →recent activity
Analyzing
Block #85,668,902
11 transactions · 9 stateful · 2026-07-05 02:17:00 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,668,902 · 11 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b59ced7…a923
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xafd76a8a…726f
0x065c9d…c394
4 touches
1 conflict
0x5657d0d6…44b3
0x065c9d…c394
2 touches
0 conflicts
0x72bb9716…1c5c
0x065c9d…c394
2 touches
0 conflicts
0x9e70cc41…d8d8
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
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 0x9b59ced7e0…f5a923
Audit this contract →
← previous block·next block →recent activity