← previous blocknext block →recent activity

Analyzing

Block #109,144,038

18 transactions · 15 stateful · 2026-09-29 21:32:23 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #109,144,038  ·  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

0x17a7f697…dcb2

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x8dbd33a8…eca5

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0040

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0052

0x1b6862…e19c

8 touches
6 conflicts

0x57d3b231…a40d

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

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 0x17a7f69751…9bdcb2

← previous block·next block →recent activity