← previous blocknext block →recent activity

Analyzing

Block #109,133,668

19 transactions · 16 stateful · 2026-09-29 20:39:47 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #109,133,668  ·  19 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

0x78694995…f668

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xa3d33c28…c2f4

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0052

0x1b6862…e19c

8 touches
6 conflicts

0x41629d02…0e43

0x1b6862…e19c

8 touches
6 conflicts

0xb640c711…082a

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 0x7869499549…adf668

← previous block·next block →recent activity