← previous blocknext block →recent activity
Analyzing
Block #106,425,929
22 transactions · 18 stateful · 2026-09-20 09:20:39 UTC
Parallelism
55/100
Blocked
61%
Avg conflicts / tx
1.59
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,425,929 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w719w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84611dd3…b344
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002b
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001b
0x1b6862…e19c
16 touches
28 conflicts
0x7f85d890…b848
0xd32edf…ff58
15 touches
28 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 0x84611dd3a3…f2b344
Audit this contract →
← previous block·next block →recent activity