← previous blocknext block →recent activity
Analyzing
Block #109,137,875
13 transactions · 13 stateful · 2026-09-29 21:00:57 UTC
Parallelism
54/100
Blocked
62%
Avg conflicts / tx
1.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,137,875 · 13 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
1w02w13w24w35w47w410w111w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe01158fd…f97d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd4cd5501…70e9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x22e1b157…d836
0x1b6862…e19c
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 0xe01158fdb6…86f97d
Audit this contract →
← previous block·next block →recent activity