← previous blocknext block →recent activity
Analyzing
Block #80,642,135
41 transactions · 32 stateful · 2026-06-11 19:30:25 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1.2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,642,135 · 41 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w69w710w815w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f3d066b…8f06
0xd32edf…ff58
17 touches
36 conflicts
0x91220b8f…7a08
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
36 conflicts on slot 0x6f3d066bc0…c28f06
Audit this contract →
← previous block·next block →recent activity