← previous blocknext block →recent activity
Analyzing
Block #80,683,198
22 transactions · 17 stateful · 2026-06-12 00:04:07 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,683,198 · 22 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
1w02w13w24w36w47w512w513w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x244e9e57…8e0d
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0x6fae99…a56d
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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
15 conflicts on slot 0x244e9e57cd…a28e0d
Audit this contract →
← previous block·next block →recent activity