← previous blocknext block →recent activity
Analyzing
Block #109,229,260
15 transactions · 14 stateful · 2026-09-30 04:41:17 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,229,260 · 15 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
1w02w13w24w35w47w18w110w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc2aacf41…5500
0x1b6862…e19c
10 touches
10 conflicts
0x5b785c57…755d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0054
0x1b6862…e19c
6 touches
3 conflicts
0xd5f4af47…cea4
0x1b6862…e19c
6 touches
3 conflicts
0xd749e32f…5cc7
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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…000013
Audit this contract →
← previous block·next block →recent activity