← previous blocknext block →recent activity
Analyzing
Block #80,590,532
31 transactions · 22 stateful · 2026-06-11 13:45:51 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,590,532 · 31 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
1w04w05w07w08w19w111w212w318w221w426w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33f84d87…32ec
0xd32edf…ff58
9 touches
10 conflicts
0x52d65d97…1c96
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x40c9380a…2115
0xa6afd3…d132
4 touches
1 conflict
0x0eb4fd49…10ef
0xa6afd3…d132
3 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 0x33f84d87cb…3f32ec
Audit this contract →
← previous block·next block →recent activity