← previous blocknext block →recent activity
Analyzing
Block #106,186,138
32 transactions · 30 stateful · 2026-09-19 13:13:49 UTC
Parallelism
84/100
Blocked
63%
Avg conflicts / tx
1.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,186,138 · 32 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
1w02w13w24w35w46w07w18w19w218w219w320w321w422w326w127w228w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb86
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0x52b428f5…93c0
0xd32edf…ff58
9 touches
10 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 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)
10 conflicts on slot 0xcb45d9d62a…b1cb86
Audit this contract →
← previous block·next block →recent activity