← previous blocknext block →recent activity

Analyzing

Block #110,207,661

19 transactions · 18 stateful · 2026-10-03 14:46:17 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #110,207,661  ·  19 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

0x6235638c…643d

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…002f

0x1b6862…e19c

10 touches
10 conflicts

0x1a250cd1…c8d6

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

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 0x6235638cfd…ef643d

← previous block·next block →recent activity