← previous blocknext block →recent activity
Analyzing
Block #85,992,354
22 transactions · 20 stateful · 2026-07-06 14:13:30 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,992,354 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w47w08w110w411w013w115w520w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2cb58c…b268
0x065c9d…c394
9 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x2b98c9a9…bc31
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x1da7723c…80a9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0x5e2cb58cb5…16b268
Audit this contract →
← previous block·next block →recent activity