← previous blocknext block →recent activity
Analyzing
Block #80,534,339
30 transactions · 19 stateful · 2026-06-11 07:30:08 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #80,534,339 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x630d9915…9e88
0xd32edf…ff58
21 touches
55 conflicts
0xb6d6d740…e91f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 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
55 conflicts on slot 0x630d9915f4…509e88
Audit this contract →
← previous block·next block →recent activity