Block #72,317,569

← previous blocknext block →recent activity

Analyzing

Block #72,317,569

8 transactions · 7 stateful · 2026-05-04 05:57:58 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,317,569  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd6f2ecb9…6b29

0x065c9d…c394

4 touches
1 conflict

0x2f685f5b…3d8e

0x065c9d…c394

3 touches
1 conflict

0x431e73aa…979d

0x065c9d…c394

3 touches
1 conflict

0x380980c6…3f68

0x065c9d…c394

2 touches
0 conflicts

0x4befa789…b6e5

0x065c9d…c394

2 touches
0 conflicts

0x95867120…c40e

0x065c9d…c394

2 touches
0 conflicts

0x9921b36c…081c

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 0x0000000000…00003d

← previous block·next block →recent activity