← previous blocknext block →recent activity
Analyzing
Block #86,851,333
34 transactions · 24 stateful · 2026-07-10 13:53:55 UTC
Parallelism
85/100
Blocked
54%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,851,333 · 34 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
1w02w13w24w37w210w012w013w114w215w116w117w020w323w424w132w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf5de301…444f
0xd32edf…ff58
7 touches
6 conflicts
0xbcdee322…f454
0xa6afd3…d132
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd45bf713…49a6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
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 0xcf5de301ca…86444f
Audit this contract →
← previous block·next block →recent activity