← previous blocknext block →recent activity
Analyzing
Block #80,164,083
33 transactions · 21 stateful · 2026-06-09 14:22:29 UTC
Parallelism
85/100
Blocked
57%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,164,083 · 33 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
1w02w13w26w210w112w313w314w322w023w124w329w231w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40d58f54…2cb9
0xd32edf…ff58
7 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x7322fb4a…635e
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
6 conflicts on slot 0x40d58f5471…9f2cb9
Audit this contract →
← previous block·next block →recent activity