← previous blocknext block →recent activity
Analyzing
Block #80,256,476
33 transactions · 27 stateful · 2026-06-10 00:38:40 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,256,476 · 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
1w02w13w24w35w413w014w116w017w119w229w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x649fbb22…0f5c
0xd32edf…ff58
9 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x179fe783…6945
0xa6afd3…d132
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
10 conflicts on slot 0x649fbb222b…460f5c
Audit this contract →
← previous block·next block →recent activity