← previous blocknext block →recent activity
Analyzing
Block #85,971,144
15 transactions · 13 stateful · 2026-07-06 11:51:40 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,971,144 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a964cd9…5fb3
0xd32edf…ff58
7 touches
6 conflicts
0xe06bbb2e…9417
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
6 touches
3 conflicts
0x5dbdc6b0…c5ed
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xea2d3331…6e33
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
6 conflicts on slot 0x1a964cd988…755fb3
Audit this contract →
← previous block·next block →recent activity