← previous blocknext block →recent activity
Analyzing
Block #86,306,478
16 transactions · 13 stateful · 2026-07-08 01:10:36 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,306,478 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w110w411w514w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb0d0b16…923a
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0xd45e7a3b…85f7
0x34b655…2a6f
4 touches
1 conflict
0xddc0f050…9726
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
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
15 conflicts on slot 0xbb0d0b168f…4f923a
Audit this contract →
← previous block·next block →recent activity