← previous blocknext block →recent activity
Analyzing
Block #80,502,260
20 transactions · 13 stateful · 2026-06-11 03:56:35 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,502,260 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x970fb713…fd0d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x01e39429…f244
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0xb543d97e…cc3f
0x34b655…2a6f
4 touches
1 conflict
0xe8bff3cf…5740
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
10 conflicts on slot 0x970fb71306…46fd0d
Audit this contract →
← previous block·next block →recent activity