← previous blocknext block →recent activity

Analyzing

Block #79,420,324

24 transactions · 22 stateful · 2026-06-06 03:32:00 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #79,420,324  ·  24 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…0013

0x1b6862…e19c

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x7322fb4a…635f

0x1b6862…e19c

8 touches
6 conflicts

0x118d4d5e…14e0

0xd32edf…ff58

7 touches
6 conflicts

0x9dd7cf9a…cebc

0xa6afd3…d132

6 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

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