← previous blocknext block →recent activity
Analyzing
Block #83,639,638
22 transactions · 18 stateful · 2026-06-25 16:50:45 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,639,638 · 22 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
1w02w13w24w35w410w011w112w213w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdab35ab9…d457
0xd32edf…ff58
9 touches
10 conflicts
0xda5e0705…ecb9
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0a8f8b9c…3046
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 0xdab35ab910…2ad457
Audit this contract →
← previous block·next block →recent activity