← previous blocknext block →recent activity
Analyzing
Block #86,620,136
28 transactions · 20 stateful · 2026-07-09 12:08:15 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,620,136 · 28 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
1w02w13w24w35w46w58w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd6beed5…2574
0xd32edf…ff58
15 touches
28 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e638
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 0xdd6beed556…e12574
Audit this contract →
← previous block·next block →recent activity