Block #72,425,710

← previous blocknext block →recent activity

Analyzing

Block #72,425,710

7 transactions · 7 stateful · 2026-05-04 17:58:34 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x1e499c6a…d332

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x62821c3d…498d

0x065c9d…c394

3 touches
1 conflict

0x714d3873…7b2b

0x065c9d…c394

3 touches
1 conflict

0x43e085ac…2b6a

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x90579b1b…3fda

0x065c9d…c394

2 touches
0 conflicts

0xddafe75a…3d7a

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 0x1e499c6ad9…3cd332

← previous block·next block →recent activity