Block #72,301,384

← previous blocknext block →recent activity

Analyzing

Block #72,301,384

9 transactions · 8 stateful · 2026-05-04 04:10:11 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,384  ·  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

0xcfab2ee0…1384

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x90c1fed7…8337

0x065c9d…c394

4 touches
1 conflict

0xc10ef9c8…0ef6

0x065c9d…c394

3 touches
1 conflict

0x06458c39…ddba

0x065c9d…c394

3 touches
1 conflict

0xac02fc50…1c28

0x065c9d…c394

3 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0x1a4b4152…0a08

0x8d0464…4402

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 0xcfab2ee055…ec1384

← previous block·next block →recent activity