← previous blocknext block →recent activity

Analyzing

Block #108,923,142

15 transactions · 14 stateful · 2026-09-29 02:56:56 UTC

Parallelism

73/100

Blocked

57%

Avg conflicts / tx

1.07

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,923,142  ·  15 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

0xf34802b3…9f12

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x11a75ebf…a215

0xd32edf…ff58

7 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0056

0x1b6862…e19c

4 touches
1 conflict

0x294b11ce…13b7

0x1b6862…e19c

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 0xf34802b39f…f89f12

← previous block·next block →recent activity