← previous blocknext block →recent activity
Analyzing
Block #109,230,334
25 transactions · 22 stateful · 2026-09-30 04:46:41 UTC
Parallelism
60/100
Blocked
55%
Avg conflicts / tx
2.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,230,334 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w923w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0xd4c913d7…343b
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x1c125d30…c5e3
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0054
0x1b6862…e19c
16 touches
28 conflicts
0x8bd52e92…4b54
0x1b6862…e19c
16 touches
28 conflicts
0x8c94d005…4557
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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)
45 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity