Block #72,425,834

← previous blocknext block →recent activity

Analyzing

Block #72,425,834

14 transactions · 13 stateful · 2026-05-04 17:59:24 UTC

Parallelism

71/100

Blocked

31%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,425,834  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4d4cc8b9…d76e

0x065c9d…c394

4 touches
1 conflict

0x32705262…2acc

0xd32edf…ff58

3 touches
1 conflict

0x3b8670b6…2ce5

0x065c9d…c394

3 touches
1 conflict

0x5762ad28…717e

0x065c9d…c394

3 touches
1 conflict

0xd6f2e607…9c61

0x065c9d…c394

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

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity