← previous blocknext block →recent activity

Analyzing

Block #109,064,973

18 transactions · 18 stateful · 2026-09-29 14:53:35 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.28

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #109,064,973  ·  18 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

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xba5743c7…21bf

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x7bcc9718…abce

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0051

0x1b6862…e19c

8 touches
6 conflicts

0x063eca74…c2e2

0x1b6862…e19c

8 touches
6 conflicts

0x5c421c70…c2eb

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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)

10 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity