← previous blocknext block →recent activity

Analyzing

Block #108,652,615

18 transactions · 17 stateful · 2026-09-28 04:11:51 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,652,615  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0a6cb118…4caa

0x1b6862…e19c

8 touches
6 conflicts

0xa69bb4e1…f2bb

0x34b655…2a6f

8 touches
6 conflicts

0xf5dc501b…831c

0x34b655…2a6f

8 touches
6 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x51798e0c…6980

0xd32edf…ff58

7 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)

6 conflicts on slot 0x0a6cb11882…264caa

← previous block·next block →recent activity