← previous blocknext block →recent activity
Analyzing
Block #80,220,501
26 transactions · 22 stateful · 2026-06-09 20:38:46 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,220,501 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w18w29w110w311w414w415w016w217w318w419w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2635c678…ed3d
0xd32edf…ff58
11 touches
15 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x394c3833…b4ae
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0x2635c67875…45ed3d
Audit this contract →
← previous block·next block →recent activity