← previous blocknext block →recent activity

Analyzing

Block #109,056,576

23 transactions · 19 stateful · 2026-09-29 14:11:15 UTC

Parallelism

78/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #109,056,576  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x485d2778…aa5a

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xd815820a…b1af

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0051

0x1b6862…e19c

8 touches
6 conflicts

0x062a584e…0f5a

0x1b6862…e19c

8 touches
6 conflicts

0x7fb41b08…7e1e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

10 conflicts on slot 0x485d277847…5daa5a

← previous block·next block →recent activity