← previous blocknext block →recent activity
Analyzing
Block #80,491,962
39 transactions · 27 stateful · 2026-06-11 02:48:01 UTC
Parallelism
87/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,491,962 · 39 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
1w02w13w24w316w017w018w022w323w428w030w432w138w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a91b64a…a5cc
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x158accef…4c74
0xa6afd3…d132
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 0x1a91b64a8f…89a5cc
Audit this contract →
← previous block·next block →recent activity