← previous blocknext block →recent activity
Analyzing
Block #106,922,207
16 transactions · 16 stateful · 2026-09-22 02:59:30 UTC
Parallelism
56/100
Blocked
63%
Avg conflicts / tx
1.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,922,207 · 16 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
2w03w14w25w06w17w28w29w310w411w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x906a08bc…2713
0xd32edf…ff58
11 touches
15 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0x465fd867…34a7
0x34b655…2a6f
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)
15 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity