← previous blocknext block →recent activity
Analyzing
Block #80,292,471
22 transactions · 17 stateful · 2026-06-10 04:38:40 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,292,471 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w38w310w411w013w114w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd787e0…b648
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…4734
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x4f2daaf7…f9e7
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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 0x6bd787e015…e5b648
Audit this contract →
← previous block·next block →recent activity