← previous blocknext block →recent activity
Analyzing
Block #80,266,969
25 transactions · 18 stateful · 2026-06-10 01:48:40 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,266,969 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w09w112w314w315w021w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728da6aa…3c44
0xd32edf…ff58
7 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc84b3e88…270b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
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 0x728da6aaaf…493c44
Audit this contract →
← previous block·next block →recent activity