← previous blocknext block →recent activity
Analyzing
Block #74,455,040
25 transactions · 19 stateful · 2026-05-14 03:25:04 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,455,040 · 25 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
1w02w13w24w38w313w014w117w418w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0000
0xcc67aa…c71c
8 touches
6 conflicts
0x00000000…0001
0xcc67aa…c71c
8 touches
6 conflicts
0x44ad89ba…cf83
0x5c2513…7777
8 touches
6 conflicts
0xce2b6650…ecc3
0x5c2513…7777
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 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…000012
Audit this contract →
← previous block·next block →recent activity