← previous blocknext block →recent activity
Analyzing
Block #86,298,158
23 transactions · 18 stateful · 2026-07-08 00:15:02 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,298,158 · 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
1w02w13w24w35w48w09w111w512w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x162828b5…d713
0xd32edf…ff58
11 touches
15 conflicts
0xb03ccb40…ede4
0x34b655…2a6f
4 touches
1 conflict
0xd9654d3e…7c6f
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 conflicts
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 0x162828b56e…f1d713
Audit this contract →
← previous block·next block →recent activity