← previous blocknext block →recent activity
Analyzing
Block #85,653,314
22 transactions · 19 stateful · 2026-07-05 00:33:16 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,653,314 · 22 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
1w02w13w24w35w48w510w311w512w616w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb523a509…d51f
0xd32edf…ff58
13 touches
21 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x10c19272…7442
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xb523a50916…87d51f
Audit this contract →
← previous block·next block →recent activity