← previous blocknext block →recent activity
Analyzing
Block #109,132,454
19 transactions · 19 stateful · 2026-09-29 20:33:40 UTC
Parallelism
47/100
Blocked
63%
Avg conflicts / tx
2.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,132,454 · 19 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w914w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x2b093939…9084
0x1b6862…e19c
20 touches
45 conflicts
0xe8883a0f…f85a
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0052
0x1b6862…e19c
14 touches
21 conflicts
0x2b88485c…a733
0x1b6862…e19c
14 touches
21 conflicts
0x6c0daab7…4a63
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
45 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity