Block #72,425,677

← previous blocknext block →recent activity

Analyzing

Block #72,425,677

6 transactions · 5 stateful · 2026-05-04 17:58:20 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,425,677  ·  6 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

0x1c601885…a733

0x065c9d…c394

4 touches
1 conflict

0x4f2e57a8…9769

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc6ac9dab…c0db

0x065c9d…c394

3 touches
1 conflict

0x2efa30f4…1459

0x065c9d…c394

3 touches
1 conflict

0x50c7cce5…4eb6

0x065c9d…c394

3 touches
1 conflict

0x5f38b346…b42a

0x065c9d…c394

3 touches
1 conflict

0x2e4bdd4e…19a1

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

1 conflict on slot 0x1c60188553…4fa733

← previous block·next block →recent activity