← previous blocknext block →recent activity

Analyzing

Block #107,815,347

20 transactions · 20 stateful · 2026-09-25 05:57:28 UTC

Parallelism

55/100

Blocked

55%

Avg conflicts / tx

1.4

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #107,815,347  ·  20 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…0013

0x1b6862…e19c

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc7679110…572d

0x34b655…2a6f

8 touches
6 conflicts

0x2a880840…7365

0x34b655…2a6f

8 touches
6 conflicts

0xd4c913d7…343f

0x1b6862…e19c

8 touches
6 conflicts

0xaa2af2e4…3831

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 0x0000000000…000013

← previous block·next block →recent activity