← previous blocknext block →recent activity
Analyzing
Block #106,362,133
11 transactions · 11 stateful · 2026-09-20 03:59:36 UTC
Parallelism
36/100
Blocked
64%
Avg conflicts / tx
1.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,362,133 · 11 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
1w02w14w05w26w37w48w59w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x4a976285…0031
0xd32edf…ff58
11 touches
15 conflicts
0x3ca268be…8865
0x34b655…2a6f
6 touches
3 conflicts
0x23592ab4…9ba8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity