← previous blocknext block →recent activity
Analyzing
Block #86,168,628
24 transactions · 22 stateful · 2026-07-07 09:50:10 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,168,628 · 24 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
1w02w13w24w37w411w012w116w317w018w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b05a9c5…e1ec
0xd32edf…ff58
7 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x38b5b2ce…c5bb
0xfa32f9…f3f0
6 touches
3 conflicts
0x7aad02c6…b979
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 0x3b05a9c5aa…fee1ec
Audit this contract →
← previous block·next block →recent activity