← previous blocknext block →recent activity
Analyzing
Block #85,658,589
22 transactions · 20 stateful · 2026-07-05 01:08:21 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1.95
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,658,589 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w816w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdc6054e…fb24
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
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
36 conflicts on slot 0xfdc6054e5a…bafb24
Audit this contract →
← previous block·next block →recent activity