← previous blocknext block →recent activity
Analyzing
Block #80,226,561
35 transactions · 32 stateful · 2026-06-09 21:19:03 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.89
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,226,561 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w811w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67f8f8db…0f64
0xd32edf…ff58
17 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x928d6b23…5374
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
36 conflicts on slot 0x67f8f8db39…090f64
Audit this contract →
← previous block·next block →recent activity