← previous blocknext block →recent activity

Analyzing

Block #108,873,878

21 transactions · 17 stateful · 2026-09-28 22:48:37 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,873,878  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6235638c…643a

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

8 touches
6 conflicts

0xb4d33bdd…5a05

0xd32edf…ff58

7 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

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)

6 conflicts on slot 0x6235638cfd…ef643a

← previous block·next block →recent activity