← previous blocknext block →recent activity
Analyzing
Block #85,961,170
28 transactions · 24 stateful · 2026-07-06 10:45:12 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,961,170 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w112w513w019w520w623w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7531f3a…3678
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd5a25205…6459
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
15 conflicts on slot 0xf7531f3a7d…e33678
Audit this contract →
← previous block·next block →recent activity