← previous blocknext block →recent activity
Analyzing
Block #80,254,306
18 transactions · 13 stateful · 2026-06-10 00:24:11 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,254,306 · 18 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
1w02w13w25w19w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c6e6f32…4d77
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x6b7dd20e…ee2a
0x065c9d…c394
4 touches
1 conflict
0xd0ec60a1…d247
0x1b6862…e19c
4 touches
1 conflict
0xbe296b44…6a7c
0xa6afd3…d132
3 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
2 touches
0 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 0x5c6e6f32e6…f94d77
Audit this contract →
← previous block·next block →recent activity