← previous blocknext block →recent activity

Analyzing

Block #75,530,364

17 transactions · 14 stateful · 2026-05-19 03:19:24 UTC

Parallelism

82/100

Blocked

57%

Avg conflicts / tx

0.59

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,530,364  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8a35acfb…d1a8

0x8d66a4…3095

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0x9bc03909…42ed

0xd32edf…ff58

5 touches
3 conflicts

0x0335ae80…8414

0x8d66a4…3095

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