← previous blocknext block →recent activity
Analyzing
Block #75,198,957
20 transactions · 17 stateful · 2026-05-17 14:16:24 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,198,957 · 20 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
1w02w13w24w35w46w47w08w510w515w416w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x93afca4c…b47a
0x1b6862…e19c
8 touches
6 conflicts
0x0fee7de6…e423
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0004
0xd5b70d…615b
6 touches
3 conflicts
0x18aed20c…48f3
0x000000…012a
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
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…000015
Audit this contract →
← previous block·next block →recent activity