← previous blocknext block →recent activity
Analyzing
Block #106,403,156
30 transactions · 29 stateful · 2026-09-20 07:26:03 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,403,156 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w18w29w014w315w419w520w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0xfea1ba19…0db8
0xd32edf…ff58
11 touches
15 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9b7187dd…3085
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)
15 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity