← previous blocknext block →recent activity

Analyzing

Block #111,666,752

25 transactions · 25 stateful · 2026-10-08 17:13:52 UTC

Parallelism

56/100

Blocked

72%

Avg conflicts / tx

2.68

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #111,666,752  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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…aa5e

0x1b6862…e19c

20 touches
45 conflicts

0x00000000…0015

0x1b6862…e19c

20 touches
45 conflicts

0x00000000…0013

0x1b6862…e19c

20 touches
45 conflicts

0x0a1de18c…38f1

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…0055

0x1b6862…e19c

18 touches
36 conflicts

0x062a584e…0f5e

0x1b6862…e19c

18 touches
36 conflicts

0x7fb41b08…7e1e

0x1b6862…e19c

18 touches
36 conflicts

0x00000000…0012

0x1b6862…e19c

18 touches
36 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)

45 conflicts on slot 0x485d277847…5daa5e

← previous block·next block →recent activity