← previous blocknext block →recent activity

Analyzing

Block #83,876,348

25 transactions · 20 stateful · 2026-06-26 19:10:07 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.4

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,876,348  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0xd4aa9d04…fc3e

0xd32edf…ff58

5 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b16149e…7d4d

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 0x0000000000…000012

← previous block·next block →recent activity