Block #72,301,025

← previous blocknext block →recent activity

Analyzing

Block #72,301,025

11 transactions · 9 stateful · 2026-05-04 04:07:48 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x4b2e3451…da37

0x065c9d…c394

4 touches
1 conflict

0x7c759cc5…8525

0x065c9d…c394

4 touches
1 conflict

0xf5fcce89…7e1f

0x065c9d…c394

3 touches
1 conflict

0x822c0fc0…8f17

0x065c9d…c394

3 touches
1 conflict

0xb71dd5b5…490b

0x065c9d…c394

3 touches
1 conflict

0x39109867…0a63

0x065c9d…c394

2 touches
0 conflicts

0x6babf30d…e57e

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