← previous blocknext block →recent activity
Analyzing
Block #86,335,587
17 transactions · 16 stateful · 2026-07-08 04:25:05 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,335,587 · 17 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
1w02w13w24w05w17w38w29w413w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8352f59b…2616
0xd32edf…ff58
9 touches
10 conflicts
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0xb4aa41e0…f123
0x34b655…2a6f
6 touches
3 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x2054b296…96c0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x81d178ba…d801
0x34b655…2a6f
4 touches
1 conflict
0x9f287382…28e5
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
10 conflicts on slot 0x8352f59b20…032616
Audit this contract →
← previous block·next block →recent activity