← previous blocknext block →recent activity

Analyzing

Block #107,838,860

18 transactions · 17 stateful · 2026-09-25 07:55:48 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,838,860  ·  18 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

0x1f8a126c…9aa8

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x17c4f72b…a870

0xd32edf…ff58

7 touches
6 conflicts

0x25144f94…1854

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

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 0x1f8a126c15…f29aa8

← previous block·next block →recent activity