← previous blocknext block →recent activity
Analyzing
Block #86,629,482
35 transactions · 25 stateful · 2026-07-09 13:10:38 UTC
Parallelism
74/100
Blocked
60%
Avg conflicts / tx
1.26
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,629,482 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w611w716w723w829w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0017fceb…16e5
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfac61869…a562
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
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
36 conflicts on slot 0x0017fceb55…2816e5
Audit this contract →
← previous block·next block →recent activity