← previous blocknext block →recent activity
Analyzing
Block #86,250,250
39 transactions · 34 stateful · 2026-07-07 18:55:20 UTC
Parallelism
80/100
Blocked
62%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,250,250 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w38w49w510w522w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b7602ae…d096
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb56f0740…7542
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8735
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x0b7602ae3f…72d096
Audit this contract →
← previous block·next block →recent activity