← previous blocknext block →recent activity
Analyzing
Block #86,222,159
66 transactions · 41 stateful · 2026-07-07 15:47:37 UTC
Parallelism
85/100
Blocked
61%
Avg conflicts / tx
1.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,222,159 · 66 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w411w413w514w633w734w836w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7669616a…39b7
0xd32edf…ff58
17 touches
36 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x394c3833…b4ae
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
36 conflicts on slot 0x7669616a85…c039b7
Audit this contract →
← previous block·next block →recent activity