← previous blocknext block →recent activity
Analyzing
Block #109,131,808
18 transactions · 17 stateful · 2026-09-29 20:30:25 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,131,808 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w415w016w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58eca50…59f7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x3da6cd28…d8e9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x73714323…0a75
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 0xf58eca505b…9a59f7
Audit this contract →
← previous block·next block →recent activity