← previous blocknext block →recent activity

Analyzing

Block #112,584,334

30 transactions · 29 stateful · 2026-10-11 22:10:35 UTC

Parallelism

87/100

Blocked

24%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #112,584,334  ·  30 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x394c3833…b4ad

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x7839ac24…21fa

0xd32edf…ff58

7 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x178fe051…465a

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x3e1329b8…deca

0x34b655…2a6f

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)

6 conflicts on slot 0x394c38330b…c9b4ad

← previous block·next block →recent activity