Block #72,284,430

← previous blocknext block →recent activity

Analyzing

Block #72,284,430

15 transactions · 11 stateful · 2026-05-04 02:16:35 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x73c15e8f…b6a7

0x065c9d…c394

4 touches
2 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd0a3a816…3a13

0x065c9d…c394

3 touches
1 conflict

0xeb06e2bd…9d9b

0x065c9d…c394

3 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21bf

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity