← previous blocknext block →recent activity
Analyzing
Block #73,753,729
29 transactions · 23 stateful · 2026-05-10 21:31:03 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,753,729 · 29 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
2w03w14w05w06w07w18w29w010w111w212w314w115w216w326w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd381d0e5…7436
0x1b6862…e19c
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xe4853af4…8c29
0xd32edf…ff58
7 touches
6 conflicts
0x8a35acfb…d1ad
0x8d66a4…3095
6 touches
3 conflicts
0xe89e1a22…ce49
0x8d66a4…3095
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 0xd381d0e5e6…4e7436
Audit this contract →
← previous block·next block →recent activity