← previous blocknext block →recent activity
Analyzing
Block #109,169,626
28 transactions · 23 stateful · 2026-09-29 23:41:08 UTC
Parallelism
64/100
Blocked
74%
Avg conflicts / tx
2.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,169,626 · 28 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
2w03w14w25w37w48w59w611w412w513w114w215w319w424w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 conflicts
0x6235638c…6438
0x1b6862…e19c
14 touches
21 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x7aa70f52…6527
0xd32edf…ff58
13 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 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)
21 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity