← previous blocknext block →recent activity
Analyzing
Block #85,173,725
20 transactions · 18 stateful · 2026-07-02 19:19:26 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,173,725 · 20 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
1w02w13w24w36w47w58w09w410w111w214w616w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x725736ab…e17e
0xd32edf…ff58
9 touches
10 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
5 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
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
10 conflicts on slot 0x725736abe2…5ae17e
Audit this contract →
← previous block·next block →recent activity