← previous blocknext block →recent activity
Analyzing
Block #85,669,363
24 transactions · 21 stateful · 2026-07-05 02:20:05 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,669,363 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w59w612w418w720w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b4164ea…a355
0xd32edf…ff58
9 touches
10 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x1045386d…cb8a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
10 conflicts on slot 0x4b4164ea2d…28a355
Audit this contract →
← previous block·next block →recent activity