← previous blocknext block →recent activity
Analyzing
Block #106,567,313
31 transactions · 28 stateful · 2026-09-20 21:12:17 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
1.16
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,567,313 · 31 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
1w02w13w28w09w110w212w313w416w117w519w627w229w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xdd402f67…8e82
0xd32edf…ff58
9 touches
10 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
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 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity