← previous blocknext block →recent activity

Analyzing

Block #100,788,901

24 transactions · 18 stateful · 2026-08-31 15:14:05 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,788,901  ·  24 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

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0xfe45073e…6315

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x74a47d7e…4355

0xd32edf…ff58

5 touches
3 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x10ca7c55…c28d

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)

3 conflicts on slot 0xba5743c7a6…7321c1

← previous block·next block →recent activity