← previous blocknext block →recent activity
Analyzing
Block #80,820,810
21 transactions · 11 stateful · 2026-06-12 15:21:44 UTC
Parallelism
86/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,820,810 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5db5d2b…7d4c
0xd32edf…ff58
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x04680797…d669
0x065c9d…c394
2 touches
0 conflicts
0x358f2d88…cf36
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x3833c9c9…14dd
0x1111b3…4111
2 touches
0 conflicts
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
3 conflicts on slot 0xb5db5d2be2…997d4c
Audit this contract →
← previous block·next block →recent activity