← previous blocknext block →recent activity
Analyzing
Block #80,642,196
52 transactions · 37 stateful · 2026-06-11 19:30:50 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,642,196 · 52 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
1w02w13w24w35w46w57w68w712w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93f36f50…100a
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0002
0xb18bf8…e9f3
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x93f36f502d…c4100a
Audit this contract →
← previous block·next block →recent activity