← previous blocknext block →recent activity
Analyzing
Block #86,389,919
33 transactions · 30 stateful · 2026-07-08 10:28:09 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.03
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,389,919 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w17w58w69w725w826w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f1e1ae2…b394
0xd32edf…ff58
13 touches
21 conflicts
0xda6b535e…6d69
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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 0x5f1e1ae22f…6fb394
Audit this contract →
← previous block·next block →recent activity