← previous blocknext block →recent activity
Analyzing
Block #85,708,178
10 transactions · 8 stateful · 2026-07-05 06:40:01 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,708,178 · 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
1w04w05w17w1
- 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
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0x03d9a8a3…8621
0x065c9d…c394
2 touches
0 conflicts
0x18ffb33d…0738
0x065c9d…c394
2 touches
0 conflicts
0x27a8046f…1317
0x065c9d…c394
2 touches
0 conflicts
0xc19523c6…5e06
0x065c9d…c394
2 touches
0 conflicts
0xcaae9361…0d84
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity