← previous blocknext block →recent activity
Analyzing
Block #106,954,338
17 transactions · 16 stateful · 2026-09-22 05:41:15 UTC
Parallelism
65/100
Blocked
69%
Avg conflicts / tx
1.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,954,338 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w27w08w19w210w412w013w514w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
12 touches
15 conflicts
0x4da61ecd…1a20
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xc824469a…6425
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)
15 conflicts on slot 0x0000000000…00001d
Audit this contract →
← previous block·next block →recent activity