Block #72,576,251

← previous blocknext block →recent activity

Analyzing

Block #72,576,251

10 transactions · 7 stateful · 2026-05-05 10:40:59 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,576,251  ·  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

0x08da00b0…afd1

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x031402cd…a9d8

0x065c9d…c394

3 touches
1 conflict

0xf36a0930…3e99

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x39e56c78…9be2

0x065c9d…c394

2 touches
0 conflicts

0x4f0818da…d6a8

0x065c9d…c394

2 touches
0 conflicts

0xe967c8df…6a13

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 0x08da00b066…70afd1

← previous block·next block →recent activity