← previous blocknext block →recent activity
Analyzing
Block #74,398,763
30 transactions · 21 stateful · 2026-05-13 21:10:26 UTC
Parallelism
70/100
Blocked
57%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,398,763 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w522w623w024w125w226w328w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x580c6fe7…0fe4
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0xaa413712…2ca7
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0000
0x2c492d…444e
10 touches
10 conflicts
0x00000000…0001
0x2c492d…444e
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xc740dd24…9801
0x3bd359…433a
10 touches
10 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)
15 conflicts on slot 0x580c6fe77a…cf0fe4
Audit this contract →
← previous block·next block →recent activity