← previous blocknext block →recent activity
Analyzing
Block #85,909,463
21 transactions · 15 stateful · 2026-07-06 05:00:25 UTC
Parallelism
76/100
Blocked
60%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,909,463 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w310w011w113w214w315w419w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01154b33…52cc
0xd32edf…ff58
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x80cdbdad…9834
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
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: FastLane: FastLaneAuctionHandler
6 conflicts on slot 0x01154b33e1…f652cc
Audit this contract →
← previous block·next block →recent activity