Block #72,429,474

← previous blocknext block →recent activity

Analyzing

Block #72,429,474

10 transactions · 9 stateful · 2026-05-04 18:23:35 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,429,474  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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…003d

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x05767989…217e

0x065c9d…c394

2 touches
0 conflicts

0x24216e94…9055

0x065c9d…c394

2 touches
0 conflicts

0x365d953f…8e00

0x065c9d…c394

2 touches
0 conflicts

0x7e438c85…f897

0x065c9d…c394

2 touches
0 conflicts

0x8f928f69…2f2a

0x065c9d…c394

2 touches
0 conflicts

0xe0e33513…1cab

0x065c9d…c394

2 touches
0 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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity