← previous blocknext block →recent activity
Analyzing
Block #80,164,436
34 transactions · 26 stateful · 2026-06-09 14:24:50 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
1.41
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,164,436 · 34 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
1w02w13w24w35w46w57w68w79w814w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c49f283…0c34
0xd32edf…ff58
17 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x48a29a03…c43b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
36 conflicts on slot 0x1c49f283ce…b90c34
Audit this contract →
← previous block·next block →recent activity