← previous blocknext block →recent activity
Analyzing
Block #80,755,006
24 transactions · 19 stateful · 2026-06-12 08:02:55 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,755,006 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w27w38w410w011w112w213w314w015w118w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e147e8f…161e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x6fae99…a56d
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x5a3732cb…edae
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 0x5e147e8fdc…67161e
Audit this contract →
← previous block·next block →recent activity