← previous blocknext block →recent activity

Analyzing

Block #106,551,479

19 transactions · 17 stateful · 2026-09-20 19:52:35 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

1.32

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #106,551,479  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…001d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

12 touches
15 conflicts

0x17ad0850…7b23

0xd32edf…ff58

11 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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)

15 conflicts on slot 0x0000000000…00001d

← previous block·next block →recent activity