← previous blocknext block →recent activity
Analyzing
Block #80,138,791
23 transactions · 18 stateful · 2026-06-09 11:33:53 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,138,791 · 23 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
0w01w02w13w25w06w18w19w310w416w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa96e58dd…e9b5
0xd32edf…ff58
9 touches
10 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x96c98bf4…14a5
0x065c9d…c394
4 touches
1 conflict
0x9d9703a9…1eeb
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
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 0xa96e58dd10…afe9b5
Audit this contract →
← previous block·next block →recent activity