← previous blocknext block →recent activity

Analyzing

Block #83,890,415

34 transactions · 20 stateful · 2026-06-26 20:43:57 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.26

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,890,415  ·  34 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

0xcb45d9d6…cb80

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x12d026ac…6bed

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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 0xcb45d9d62a…b1cb80

← previous block·next block →recent activity