← previous blocknext block →recent activity
Analyzing
Block #106,336,319
20 transactions · 14 stateful · 2026-09-20 01:49:41 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,336,319 · 20 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
2w03w14w07w28w39w410w511w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0019
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xd1b10020…0459
0xd32edf…ff58
13 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x4a45b318…9716
0x34b655…2a6f
10 touches
10 conflicts
0x4fb437cc…05f7
0x34b655…2a6f
10 touches
10 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)
21 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity