← previous blocknext block →recent activity
Analyzing
Block #80,629,060
40 transactions · 27 stateful · 2026-06-11 18:03:15 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,629,060 · 40 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
1w02w13w24w35w47w08w19w310w511w012w113w221w225w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x227db221…68a9
0xd32edf…ff58
11 touches
15 conflicts
0x90d24713…b88f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0xb18bf8…e9f3
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
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
15 conflicts on slot 0x227db2216f…2168a9
Audit this contract →
← previous block·next block →recent activity