Block #72,301,261

← previous blocknext block →recent activity

Analyzing

Block #72,301,261

11 transactions · 9 stateful · 2026-05-04 04:09:22 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,301,261  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0xc13348e5…0264

0x065c9d…c394

4 touches
1 conflict

0x7160ce22…f3aa

0x065c9d…c394

3 touches
1 conflict

0x961d9ebe…d0de

0x065c9d…c394

3 touches
1 conflict

0xbd793d94…5cde

0x065c9d…c394

3 touches
1 conflict

0x2f6a028a…99b7

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity