← previous blocknext block →recent activity
Analyzing
Block #86,319,867
29 transactions · 27 stateful · 2026-07-08 02:40:07 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
1.34
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,319,867 · 29 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
1w02w13w24w36w17w48w59w614w723w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x563ac776…f104
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9da6e429…074d
0xa6afd3…d132
6 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe01158fd…f97d
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
28 conflicts on slot 0x563ac7766a…e5f104
Audit this contract →
← previous block·next block →recent activity