← previous blocknext block →recent activity
Analyzing
Block #80,309,802
20 transactions · 17 stateful · 2026-06-10 06:34:10 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,309,802 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w28w39w410w511w612w713w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x14d1bf0e…e09a
0x1b6862…e19c
8 touches
6 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
8 touches
6 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
8 touches
6 conflicts
0x1ebc6c93…6d17
0xd32edf…ff58
7 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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: ShMonad (shMON)
6 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity