← previous blocknext block →recent activity
Analyzing
Block #85,682,200
26 transactions · 23 stateful · 2026-07-05 03:45:30 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.27
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,682,200 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w48w59w610w717w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5540f956…69e8
0x065c9d…c394
10 touches
10 conflicts
0xd8986326…4de4
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 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
10 conflicts on slot 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity