← previous blocknext block →recent activity
Analyzing
Block #106,282,246
43 transactions · 34 stateful · 2026-09-19 21:17:35 UTC
Parallelism
79/100
Blocked
68%
Avg conflicts / tx
1.47
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,282,246 · 43 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w49w512w216w423w424w525w126w235w639w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6cb118…4ca3
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x65903ef9…2567
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xddd20e39…d524
0x34b655…2a6f
10 touches
10 conflicts
0x82765add…5bd3
0xd32edf…ff58
9 touches
10 conflicts
0x559447b0…eb51
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 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 0x0a6cb11882…264ca3
Audit this contract →
← previous block·next block →recent activity