← previous blocknext block →recent activity
Analyzing
Block #80,274,480
16 transactions · 14 stateful · 2026-06-10 02:38:45 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,274,480 · 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
1w02w05w09w111w113w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x833ebd97…5abb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfefd1e1d…5fed
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x66779b9e…e074
0xd32edf…ff58
3 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
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 0x833ebd9703…2b5abb
Audit this contract →
← previous block·next block →recent activity