Block #72,430,909

← previous blocknext block →recent activity

Analyzing

Block #72,430,909

8 transactions · 6 stateful · 2026-05-04 18:33:08 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,909  ·  8 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

0xf9a0ab8e…0338

0x065c9d…c394

4 touches
1 conflict

0x5bdbce30…40d6

0x065c9d…c394

3 touches
1 conflict

0x8c960d8d…5657

0x065c9d…c394

3 touches
1 conflict

0x404314de…df1a

0x3bd359…433a

2 touches
0 conflicts

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x70d3369c…4aae

0x5afd3e…7620

2 touches
0 conflicts

0x8acdefac…3358

0x5afd3e…7620

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 0xf9a0ab8e1d…b60338

← previous block·next block →recent activity