Block #72,400,076

← previous blocknext block →recent activity

Analyzing

Block #72,400,076

6 transactions · 6 stateful · 2026-05-04 15:07:44 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,400,076  ·  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

0x8d76907f…23ea

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x74c90b00…73c2

0x065c9d…c394

4 touches
1 conflict

0x02119bd9…c926

0x065c9d…c394

2 touches
0 conflicts

0x038b1f75…6c78

0x065c9d…c394

2 touches
0 conflicts

0x4a6b8dbc…2407

0x065c9d…c394

2 touches
0 conflicts

0x912d3740…d136

0x065c9d…c394

2 touches
0 conflicts

0xa73faa59…546a

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 0x8d76907fb9…1223ea

← previous block·next block →recent activity