← previous blocknext block →recent activity

Analyzing

Block #109,064,981

19 transactions · 17 stateful · 2026-09-29 14:53:37 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #109,064,981  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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…0013

0x1b6862…e19c

12 touches
15 conflicts

0x8725f80c…ff6a

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x5e3eba01…416e

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0002

0x125f12…a50b

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0051

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)

15 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity