← previous blocknext block →recent activity

Analyzing

Block #112,484,768

30 transactions · 26 stateful · 2026-10-11 13:49:37 UTC

Parallelism

67/100

Blocked

62%

Avg conflicts / tx

2.03

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #112,484,768  ·  30 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x00000000…0013

0x1b6862…e19c

20 touches
45 conflicts

0x4979282b…2935

0x1b6862…e19c

20 touches
45 conflicts

0x00000000…0015

0x1b6862…e19c

20 touches
45 conflicts

0xc72e7570…0872

0xd32edf…ff58

19 touches
45 conflicts

0x6efb1f30…9a66

0x1b6862…e19c

18 touches
36 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

18 touches
36 conflicts

0x00000000…001c

0x1b6862…e19c

18 touches
36 conflicts

0x00000000…002c

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 0x0000000000…000013

← previous block·next block →recent activity