← previous blocknext block →recent activity
Analyzing
Block #120,070,628
24 transactions · 23 stateful · 2026-11-07 03:18:15 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #120,070,628 · 24 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
1w02w13w25w06w07w18w19w310w412w123w3
- 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
0x6b1259e6…4e11
0x1b6862…e19c
8 touches
6 conflicts
0xb989b9c6…ff96
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0055
0x1b6862…e19c
6 touches
3 conflicts
0x5057d7be…407c
0x1b6862…e19c
6 touches
3 conflicts
0x85dff57e…da59
0x1b6862…e19c
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