← previous blocknext block →recent activity
Analyzing
Block #109,176,730
27 transactions · 22 stateful · 2026-09-30 00:16:53 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,176,730 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w818w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b1259e6…4e0f
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0xa0ce4714…4cf6
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0053
0x1b6862…e19c
14 touches
21 conflicts
0x5057d7be…407a
0x1b6862…e19c
14 touches
21 conflicts
0x85dff57e…da59
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
36 conflicts on slot 0x6b1259e63a…8f4e0f
Audit this contract →
← previous block·next block →recent activity