← previous blocknext block →recent activity
Analyzing
Block #109,161,738
18 transactions · 18 stateful · 2026-09-29 23:01:26 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,161,738 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w09w312w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0xc2aacf41…54ff
0x1b6862…e19c
12 touches
15 conflicts
0x300d6e1b…88a3
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0053
0x1b6862…e19c
10 touches
10 conflicts
0xd5f4af47…cea3
0x1b6862…e19c
10 touches
10 conflicts
0xd749e32f…5cc7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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)
15 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity