← previous blocknext block →recent activity

Analyzing

Block #109,177,111

24 transactions · 21 stateful · 2026-09-30 00:18:48 UTC

Parallelism

71/100

Blocked

62%

Avg conflicts / tx

1.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #109,177,111  ·  24 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0x37699b20…1071

0x1b6862…e19c

14 touches
21 conflicts

0xcf4a0ecc…5d9a

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0053

0x1b6862…e19c

12 touches
15 conflicts

0x99e733dc…1067

0x1b6862…e19c

12 touches
15 conflicts

0xc6f23e6f…da25

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

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…000013

← previous block·next block →recent activity