← previous blocknext block →recent activity
Analyzing
Block #80,234,480
14 transactions · 11 stateful · 2026-06-09 22:12:08 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,234,480 · 14 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
1w02w13w24w35w46w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa964d4a6…f9f9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x7d4f80a4…bb1a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xa964d4a67b…25f9f9
Audit this contract →
← previous block·next block →recent activity