← previous blocknext block →recent activity
Analyzing
Block #85,524,091
53 transactions · 36 stateful · 2026-07-04 10:12:47 UTC
Parallelism
60/100
Blocked
67%
Avg conflicts / tx
4.11
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #85,524,091 · 53 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w58w610w711w812w913w1014w1115w1216w1317w1430w1535w1636w1737w1838w1942w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x496754ae…2576
0xd32edf…ff58
41 touches
210 conflicts
0x00000000…0029
0x1b6862…e19c
12 touches
15 conflicts
0x4d42f16e…a6c7
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0019
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 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
210 conflicts on slot 0x496754ae80…282576
Audit this contract →
← previous block·next block →recent activity