← previous blocknext block →recent activity

Analyzing

Block #75,678,123

23 transactions · 17 stateful · 2026-05-19 19:45:34 UTC

Parallelism

87/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,678,123  ·  23 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…001c

0x1b6862…e19c

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x309ef367…e8a1

0x34b655…2a6f

6 touches
3 conflicts

0x74e485b1…d380

0x34b655…2a6f

6 touches
3 conflicts

0x62c2a2b0…d9a9

0xd32edf…ff58

5 touches
3 conflicts

0x08b8e539…b9f9

0x754704…b603

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…00001c

← previous block·next block →recent activity