← previous blocknext block →recent activity
Analyzing
Block #85,523,647
30 transactions · 24 stateful · 2026-07-04 10:09:51 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
0.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,523,647 · 30 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
1w02w13w24w35w46w510w611w012w113w215w321w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x523bb270…815e
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
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
15 conflicts on slot 0x523bb27012…23815e
Audit this contract →
← previous block·next block →recent activity