← previous blocknext block →recent activity
Analyzing
Block #80,251,049
34 transactions · 29 stateful · 2026-06-10 00:02:30 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,251,049 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w210w311w412w513w016w117w218w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f4e12e3…21c7
0x336ed4…c59c
12 touches
15 conflicts
0x00000000…000b
0x90c374…be45
12 touches
15 conflicts
0x00000000…000a
0x90c374…be45
12 touches
15 conflicts
0xc7a72d56…3b34
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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: 0x336ed437…cfc59c
15 conflicts on slot 0x9f4e12e393…0a21c7
Audit this contract →
← previous block·next block →recent activity