← previous blocknext block →recent activity
Analyzing
Block #85,898,725
39 transactions · 27 stateful · 2026-07-06 03:48:53 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,898,725 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w512w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5c9b5ee…252d
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 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: FastLane: FastLaneAuctionHandler
28 conflicts on slot 0xc5c9b5eea9…c3252d
Audit this contract →
← previous block·next block →recent activity