← previous blocknext block →recent activity
Analyzing
Block #109,161,688
17 transactions · 14 stateful · 2026-09-29 23:01:11 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,161,688 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w413w014w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c6f37ba…c207
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x8e9829bd…4dc8
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0053
0x1b6862…e19c
8 touches
6 conflicts
0x0d9d9e17…178b
0x1b6862…e19c
8 touches
6 conflicts
0x7896cd92…9c9a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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 0x6c6f37badb…87c207
Audit this contract →
← previous block·next block →recent activity