Block #72,498,253

← previous blocknext block →recent activity

Analyzing

Block #72,498,253

11 transactions · 11 stateful · 2026-05-05 02:01:38 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,498,253  ·  11 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

0xec71f457…4706

0x065c9d…c394

4 touches
1 conflict

0x3821a0af…4f0b

0x065c9d…c394

4 touches
1 conflict

0x03f99e94…b859

0x065c9d…c394

3 touches
1 conflict

0xfc3642b8…ea59

0x065c9d…c394

3 touches
1 conflict

0xaeb8aa0c…03e6

0x065c9d…c394

3 touches
1 conflict

0x8e913465…0314

0x065c9d…c394

3 touches
1 conflict

0x00bac013…a28c

0x91b81b…6d56

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