← previous blocknext block →recent activity
Analyzing
Block #119,798,927
21 transactions · 19 stateful · 2026-11-06 04:22:45 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #119,798,927 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w18w29w310w411w512w616w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6235638c…643c
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x578164b5…7f6e
0xd32edf…ff58
13 touches
21 conflicts
0xc2575a0e…f8eb
0xed3727…f3af
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)
21 conflicts on slot 0x6235638cfd…ef643c
Audit this contract →
← previous block·next block →recent activity