← previous blocknext block →recent activity
Analyzing
Block #109,004,194
19 transactions · 17 stateful · 2026-09-29 09:46:38 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,004,194 · 19 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
1w02w13w24w35w411w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e04662b…0da7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xde697df6…c769
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0057
0x1b6862…e19c
6 touches
3 conflicts
0x319f3906…963f
0x1b6862…e19c
6 touches
3 conflicts
0x4b2a9f64…3a39
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)
10 conflicts on slot 0x3e04662bca…090da7
Audit this contract →
← previous block·next block →recent activity