← previous blocknext block →recent activity
Analyzing
Block #86,324,795
21 transactions · 19 stateful · 2026-07-08 03:13:03 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,324,795 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w510w011w113w614w015w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x260dacf9…1437
0xd32edf…ff58
13 touches
21 conflicts
0x58e06bab…34cc
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
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
21 conflicts on slot 0x260dacf9b9…021437
Audit this contract →
← previous block·next block →recent activity