← previous blocknext block →recent activity

Analyzing

Block #83,863,302

17 transactions · 16 stateful · 2026-06-26 17:43:03 UTC

Parallelism

59/100

Blocked

56%

Avg conflicts / tx

1.12

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,863,302  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xd53220ed…4734

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc62a53d4…e10a

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 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)

6 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity