← previous blocknext block →recent activity

Analyzing

Block #76,603,276

19 transactions · 15 stateful · 2026-05-24 02:27:36 UTC

Parallelism

84/100

Blocked

40%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #76,603,276  ·  19 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

0x62d6e82b…a750

0x34b655…2a6f

6 touches
3 conflicts

0xc1d45948…57e8

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbb12db23…857e

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0xb0e4f69d…34e7

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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: Perpl

3 conflicts on slot 0x62d6e82b38…66a750

← previous block·next block →recent activity