← previous blocknext block →recent activity
Analyzing
Block #92,065,429
27 transactions · 19 stateful · 2026-08-01 01:00:00 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,065,429 · 27 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
1w02w13w24w35w49w516w017w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff030bb8…1eae
0xd32edf…ff58
11 touches
15 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x6affc6cd…9b19
0x34b655…2a6f
4 touches
1 conflict
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x8a1e429b…f85c
0x34b655…2a6f
4 touches
1 conflict
0xa01f2285…f16f
0x34b655…2a6f
4 touches
1 conflict
0xb8726253…292c
0x34b655…2a6f
4 touches
1 conflict
0xc048da15…6d7d
0x34b655…2a6f
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 0xff030bb8b9…411eae
Audit this contract →
← previous block·next block →recent activity