← previous blocknext block →recent activity
Analyzing
Block #107,824,007
16 transactions · 14 stateful · 2026-09-25 06:41:03 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,824,007 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w37w48w09w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x728ac8e6…dc91
0xd32edf…ff58
9 touches
10 conflicts
0x9fcf8df5…88c7
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
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 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity