← previous blocknext block →recent activity
Analyzing
Block #85,994,151
40 transactions · 33 stateful · 2026-07-06 14:25:31 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,994,151 · 40 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
1w02w13w24w35w46w59w612w425w728w533w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27e6b72e…f4a9
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
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
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
28 conflicts on slot 0x27e6b72e00…1af4a9
Audit this contract →
← previous block·next block →recent activity