← previous blocknext block →recent activity

Analyzing

Block #108,573,968

25 transactions · 23 stateful · 2026-09-27 21:35:50 UTC

Parallelism

68/100

Blocked

57%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #108,573,968  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x794b8f81…3ead

0x1b6862…e19c

10 touches
10 conflicts

0x348fda08…7e96

0x065c9d…c394

10 touches
10 conflicts

0xba38536d…2b7d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0002

0x125f12…a50b

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x7ff3a691…6054

0xd32edf…ff58

9 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)

10 conflicts on slot 0x794b8f8129…fc3ead

← previous block·next block →recent activity