← previous blocknext block →recent activity
Analyzing
Block #76,506,919
24 transactions · 20 stateful · 2026-05-23 15:46:01 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,506,919 · 24 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
1w02w13w24w35w46w310w411w513w514w416w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x4d42f16e…a6cb
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x21cc9b77…18b9
0xd32edf…ff58
13 touches
21 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)
21 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity