Block #72,429,519

← previous blocknext block →recent activity

Analyzing

Block #72,429,519

24 transactions · 16 stateful · 2026-05-04 18:23:52 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,429,519  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x3af3c419…a001

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x3af3c419aa…dba001

← previous block·next block →recent activity