← previous blocknext block →recent activity

Analyzing

Block #106,403,227

21 transactions · 20 stateful · 2026-09-20 07:26:25 UTC

Parallelism

62/100

Blocked

60%

Avg conflicts / tx

1.57

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #106,403,227  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xcb45d9d6…cb82

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…001a

0x1b6862…e19c

12 touches
15 conflicts

0x5ddd1058…e36e

0xd32edf…ff58

11 touches
15 conflicts

0x9b7187dd…3085

0x34b655…2a6f

10 touches
10 conflicts

0xfdd131fa…dbdb

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 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 0xcb45d9d62a…b1cb82

← previous block·next block →recent activity