Block #72,430,548

← previous blocknext block →recent activity

Analyzing

Block #72,430,548

7 transactions · 6 stateful · 2026-05-04 18:30:44 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,548  ·  7 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

0xb96a4937…d4b5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2c5df91b…79c0

0x065c9d…c394

4 touches
1 conflict

0x200fee29…ce6a

0x065c9d…c394

3 touches
1 conflict

0x2a86d373…e8fa

0x065c9d…c394

3 touches
1 conflict

0xa78439c9…d482

0x065c9d…c394

3 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002b

0x1b6862…e19c

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 0xb96a493732…17d4b5

← previous block·next block →recent activity