← previous blocknext block →recent activity

Analyzing

Block #100,616,263

25 transactions · 20 stateful · 2026-08-31 00:45:30 UTC

Parallelism

64/100

Blocked

75%

Avg conflicts / tx

1.64

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #100,616,263  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…001f

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…002f

0x1b6862…e19c

14 touches
21 conflicts

0xd18a8dca…4530

0x1b6862…e19c

14 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

14 touches
21 conflicts

0xe6ae1d8d…a007

0xd32edf…ff58

13 touches
21 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)

21 conflicts on slot 0x0000000000…000012

← previous block·next block →recent activity