← previous blocknext block →recent activity
Analyzing
Block #80,591,364
28 transactions · 23 stateful · 2026-06-11 13:51:24 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,591,364 · 28 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
2w03w04w05w16w211w113w014w116w217w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22d7589b…9d0e
0xd32edf…ff58
7 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
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
6 conflicts on slot 0x22d7589b36…0c9d0e
Audit this contract →
← previous block·next block →recent activity