← previous blocknext block →recent activity
Analyzing
Block #86,057,951
23 transactions · 20 stateful · 2026-07-06 21:31:35 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,057,951 · 23 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
1w02w13w24w35w46w510w011w115w016w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x970aa664…d223
0xd32edf…ff58
11 touches
15 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0xe2563272…5618
0x34b655…2a6f
4 touches
1 conflict
0xe3698f79…4512
0x34b655…2a6f
4 touches
1 conflict
0xe3c2a64e…2ce5
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xfb6cac17…e732
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
15 conflicts on slot 0x970aa66466…ebd223
Audit this contract →
← previous block·next block →recent activity