← previous blocknext block →recent activity
Analyzing
Block #80,163,758
34 transactions · 24 stateful · 2026-06-09 14:20:19 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,163,758 · 34 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
1w02w13w24w35w48w417w525w627w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d61311c…2eeb
0xd32edf…ff58
13 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x36d366fe…7adc
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8734
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0x3d61311c80…a32eeb
Audit this contract →
← previous block·next block →recent activity