← previous blocknext block →recent activity
Analyzing
Block #80,103,619
22 transactions · 17 stateful · 2026-06-09 07:39:45 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,103,619 · 22 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
1w02w13w06w17w28w010w211w312w413w518w119w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae4ac1cf…1d2d
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x3af0dd8e…0025
0x1b6862…e19c
6 touches
3 conflicts
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
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
15 conflicts on slot 0xae4ac1cfab…c91d2d
Audit this contract →
← previous block·next block →recent activity