← previous blocknext block →recent activity
Analyzing
Block #86,085,053
24 transactions · 20 stateful · 2026-07-07 00:32:18 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,085,053 · 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
1w02w13w24w35w47w18w09w112w015w116w217w321w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3de5a910…7e06
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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
10 conflicts on slot 0x3de5a9101f…1d7e06
Audit this contract →
← previous block·next block →recent activity