← previous blocknext block →recent activity
Analyzing
Block #85,873,708
35 transactions · 25 stateful · 2026-07-06 01:02:10 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,873,708 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w011w113w514w615w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34af658e…07ba
0xd32edf…ff58
11 touches
15 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x9885a25f…2926
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0x34af658e30…5607ba
Audit this contract →
← previous block·next block →recent activity