← previous blocknext block →recent activity
Analyzing
Block #85,223,032
24 transactions · 21 stateful · 2026-07-03 00:47:51 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,223,032 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w09w011w012w413w114w115w416w520w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a91e280…89a4
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
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
10 conflicts on slot 0x0a91e280d3…c089a4
Audit this contract →
← previous block·next block →recent activity