Block #72,310,063

← previous blocknext block →recent activity

Analyzing

Block #72,310,063

9 transactions · 8 stateful · 2026-05-04 05:08:01 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,310,063  ·  9 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

0x5f7064fd…fa0f

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0xcc4a72fb…372a

0x065c9d…c394

3 touches
1 conflict

0x46d1d4e9…e9a0

0x065c9d…c394

3 touches
1 conflict

0xfe009f63…438f

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 0x5f7064fd12…6afa0f

← previous block·next block →recent activity