← previous blocknext block →recent activity
Analyzing
Block #106,548,485
13 transactions · 13 stateful · 2026-09-20 19:37:31 UTC
Parallelism
62/100
Blocked
62%
Avg conflicts / tx
1.15
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,548,485 · 13 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
1w02w03w14w15w26w18w29w310w411w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xa9de9804…09a3
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x32aab5b0…0e4f
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
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 0x0000000000…00001d
Audit this contract →
← previous block·next block →recent activity