Block #72,425,569

← previous blocknext block →recent activity

Analyzing

Block #72,425,569

11 transactions · 9 stateful · 2026-05-04 17:57:37 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,425,569  ·  11 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

0x2a4b43c6…9602

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd237a289…70f9

0x065c9d…c394

3 touches
1 conflict

0x552d4ffe…e4a2

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x622790b9…3855

0x065c9d…c394

2 touches
0 conflicts

0x67699f5c…9e59

0x065c9d…c394

2 touches
0 conflicts

0x6882a8f0…0212

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 0x2a4b43c62d…479602

← previous block·next block →recent activity