← previous blocknext block →recent activity
Analyzing
Block #86,807,992
30 transactions · 27 stateful · 2026-07-10 09:04:04 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,807,992 · 30 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
1w02w13w24w35w26w411w514w618w721w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x410608f4…8a17
0xd32edf…ff58
15 touches
28 conflicts
0x273eabee…549e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x6b1259e6…4e10
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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 0x410608f487…b88a17
Audit this contract →
← previous block·next block →recent activity