Block #72,288,426

← previous blocknext block →recent activity

Analyzing

Block #72,288,426

24 transactions · 15 stateful · 2026-05-04 02:43:27 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,288,426  ·  24 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

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x6eec8464…8df2

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe5b4c4cb…680a

0x065c9d…c394

4 touches
1 conflict

0x9df33365…b6c0

0x065c9d…c394

3 touches
1 conflict

0x92df186c…c98a

0x065c9d…c394

3 touches
1 conflict

0xe91a855d…e37a

0xd32edf…ff58

3 touches
1 conflict

0x4dd1db39…a997

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity