← previous blocknext block →recent activity
Analyzing
Block #80,165,016
30 transactions · 20 stateful · 2026-06-09 14:28:43 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,165,016 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w58w69w716w627w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ed1cafe…59d0
0xd32edf…ff58
13 touches
21 conflicts
0x7d4f80a4…bb19
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…002e
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
21 conflicts on slot 0x9ed1cafe3e…f559d0
Audit this contract →
← previous block·next block →recent activity