← previous blocknext block →recent activity

Analyzing

Block #112,583,808

30 transactions · 24 stateful · 2026-10-11 22:07:56 UTC

Parallelism

77/100

Blocked

67%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #112,583,808  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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…4ca9

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0xe8b1b60c…a6a9

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0057

0x1b6862…e19c

10 touches
10 conflicts

0x03e975a9…7ce1

0x1b6862…e19c

10 touches
10 conflicts

0xca2a5765…0396

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 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 0x0a6cb11882…264ca9

← previous block·next block →recent activity