← previous blocknext block →recent activity
Analyzing
Block #109,161,326
14 transactions · 12 stateful · 2026-09-29 22:59:22 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,161,326 · 14 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
1w02w13w27w38w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c1
0x1b6862…e19c
10 touches
10 conflicts
0xe9c128d1…6233
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0053
0x1b6862…e19c
6 touches
3 conflicts
0x063eca74…c2e2
0x1b6862…e19c
6 touches
3 conflicts
0x5c421c70…c2ed
0x1b6862…e19c
6 touches
3 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 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity