← previous blocknext block →recent activity
Analyzing
Block #86,083,028
24 transactions · 21 stateful · 2026-07-07 00:18:46 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,083,028 · 24 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
1w02w13w24w35w46w07w110w011w114w219w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d52e5d9…0b80
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x2f7781d6…e632
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
0x34b655…2a6f
4 touches
1 conflict
0xe2b988ac…37d8
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 0x5d52e5d928…fc0b80
Audit this contract →
← previous block·next block →recent activity