← previous blocknext block →recent activity
Analyzing
Block #109,161,651
17 transactions · 15 stateful · 2026-09-29 23:01:00 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,161,651 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26bb6db7…f85e
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xd596f573…e344
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0053
0x1b6862…e19c
12 touches
15 conflicts
0x076a83d6…89c7
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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)
28 conflicts on slot 0x26bb6db701…d0f85e
Audit this contract →
← previous block·next block →recent activity