← previous blocknext block →recent activity
Analyzing
Block #106,393,102
18 transactions · 18 stateful · 2026-09-20 06:35:28 UTC
Parallelism
39/100
Blocked
72%
Avg conflicts / tx
2.06
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,393,102 · 18 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w38w49w510w612w113w714w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x1f37da50…59b1
0xd32edf…ff58
15 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
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)
28 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity