Block #72,429,551

← previous blocknext block →recent activity

Analyzing

Block #72,429,551

8 transactions · 7 stateful · 2026-05-04 18:24:05 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,429,551  ·  8 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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x203bad31…cf47

0x1efe02…37d6

2 touches
0 conflicts

0x49981466…6fa3

0x1efe02…37d6

2 touches
0 conflicts

0xa9137260…606c

0x1efe02…37d6

2 touches
0 conflicts

0xb772de34…3f49

0x1efe02…37d6

2 touches
0 conflicts

0x1728ed63…499c

0xea1b8e…c5ec

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

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity