← previous blocknext block →recent activity
Analyzing
Block #80,491,959
27 transactions · 24 stateful · 2026-06-11 02:48:00 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,491,959 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w110w211w112w214w018w119w220w221w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0x5e2f10b9…d038
0xd32edf…ff58
7 touches
6 conflicts
0x9a54f439…de63
0x34b655…2a6f
6 touches
3 conflicts
0xa1fb92e0…d478
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 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: Perpl
6 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity