← previous blocknext block →recent activity
Analyzing
Block #76,559,556
19 transactions · 16 stateful · 2026-05-23 21:36:40 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,559,556 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w28w210w211w012w113w314w117w4
- 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
0xc1baef71…068d
0x1b6862…e19c
8 touches
6 conflicts
0x97521e5b…1142
0xd32edf…ff58
7 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
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