← previous blocknext block →recent activity

Analyzing

Block #109,229,234

22 transactions · 20 stateful · 2026-09-30 04:41:09 UTC

Parallelism

45/100

Blocked

65%

Avg conflicts / tx

3.27

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #109,229,234  ·  22 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x1b6862…e19c

24 touches
66 conflicts

0x00000000…0013

0x1b6862…e19c

24 touches
66 conflicts

0x00000000…0015

0x1b6862…e19c

24 touches
66 conflicts

0x00000000…001b

0x1b6862…e19c

24 touches
66 conflicts

0x00000000…002b

0x1b6862…e19c

24 touches
66 conflicts

0x00000000…0040

0x1b6862…e19c

24 touches
66 conflicts

0x00000000…0054

0x1b6862…e19c

24 touches
66 conflicts

0x5cf18db5…b2e0

0x1b6862…e19c

24 touches
66 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)

66 conflicts on slot 0x0000000000…000012

← previous block·next block →recent activity