Block #72,288,389

← previous blocknext block →recent activity

Analyzing

Block #72,288,389

26 transactions · 15 stateful · 2026-05-04 02:43:12 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,288,389  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe19ff7d5…c74e

0xd32edf…ff58

11 touches
15 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe8aa0179…4676

0x065c9d…c394

3 touches
1 conflict

0x89288b34…3cd3

0x065c9d…c394

3 touches
1 conflict

0x2d24c591…a33d

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: 0xd32edf66…9fff58

15 conflicts on slot 0xe19ff7d596…00c74e

← previous block·next block →recent activity