Block #72,399,509

← previous blocknext block →recent activity

Analyzing

Block #72,399,509

18 transactions · 14 stateful · 2026-05-04 15:03:57 UTC

Parallelism

72/100

Blocked

43%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,399,509  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x68dcea7c…dd87

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x8d0166ae…f039

0x065c9d…c394

5 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x1c4dde4b…de28

0x065c9d…c394

4 touches
1 conflict

0xd31160a1…6399

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

10 conflicts on slot 0x68dcea7ca1…88dd87

← previous block·next block →recent activity