Block #72,301,201

← previous blocknext block →recent activity

Analyzing

Block #72,301,201

8 transactions · 6 stateful · 2026-05-04 04:08:58 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,301,201  ·  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

0xe4653696…8441

0x065c9d…c394

4 touches
1 conflict

0xb337333a…ec2f

0x065c9d…c394

3 touches
1 conflict

0x1bf14693…8f13

0x065c9d…c394

3 touches
1 conflict

0x90c1fed7…8337

0x065c9d…c394

3 touches
1 conflict

0x6babf30d…e57e

0x065c9d…c394

2 touches
0 conflicts

0x70a7e957…98bd

0x065c9d…c394

2 touches
0 conflicts

0xe251ab14…ad5b

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