← previous blocknext block →recent activity

Analyzing

Block #108,922,433

20 transactions · 18 stateful · 2026-09-29 02:53:21 UTC

Parallelism

45/100

Blocked

83%

Avg conflicts / tx

3.15

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #108,922,433  ·  20 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xb538c6fa…9aea

0x1b6862…e19c

22 touches
55 conflicts

0x00000000…0015

0x1b6862…e19c

22 touches
55 conflicts

0x00000000…0013

0x1b6862…e19c

22 touches
55 conflicts

0x5b72a14f…8fb9

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0056

0x1b6862…e19c

20 touches
45 conflicts

0x8bde3b8b…e5fe

0x1b6862…e19c

20 touches
45 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

20 touches
45 conflicts

0x00000000…0012

0x1b6862…e19c

20 touches
45 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)

55 conflicts on slot 0xb538c6fa35…8a9aea

← previous block·next block →recent activity