← previous blocknext block →recent activity
Analyzing
Block #80,501,792
16 transactions · 14 stateful · 2026-06-11 03:53:29 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,501,792 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w09w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1e4de02…07e9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9cf5ac50…1be9
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0x09ccdee3…ad76
0x34b655…2a6f
2 touches
0 conflicts
0x0c1aa307…ff9c
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
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: Perpl
1 conflict on slot 0xd1e4de026f…2607e9
Audit this contract →
← previous block·next block →recent activity