Block #72,394,863

← previous blocknext block →recent activity

Analyzing

Block #72,394,863

10 transactions · 8 stateful · 2026-05-04 14:32:58 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,394,863  ·  10 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

0x3274ad72…9df8

0x065c9d…c394

4 touches
1 conflict

0x37768a7d…f268

0x065c9d…c394

4 touches
1 conflict

0x48c6e5aa…cc95

0x065c9d…c394

4 touches
1 conflict

0x7325acfa…bba2

0x065c9d…c394

4 touches
1 conflict

0x9c86afa8…ffb3

0x065c9d…c394

3 touches
1 conflict

0x6364bde1…1038

0x065c9d…c394

3 touches
1 conflict

0x245938fd…59ce

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