← previous blocknext block →recent activity
Analyzing
Block #86,622,697
18 transactions · 17 stateful · 2026-07-09 12:25:20 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,622,697 · 18 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
1w02w13w24w05w38w09w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fd86ca7…a5d8
0xd32edf…ff58
7 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0x7f430e47…4cbd
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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 0x5fd86ca732…1ca5d8
Audit this contract →
← previous block·next block →recent activity