Block #72,309,856

← previous blocknext block →recent activity

Analyzing

Block #72,309,856

26 transactions · 17 stateful · 2026-05-04 05:06:39 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,309,856  ·  26 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

0x37812a2b…e3cc

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe67b8939…74be

0x065c9d…c394

3 touches
1 conflict

0x7e681cb6…d6dd

0x065c9d…c394

3 touches
1 conflict

0x00000000…0002

0x63e48b…53f2

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: 0xd32edf66…9fff58

10 conflicts on slot 0x37812a2b0a…07e3cc

← previous block·next block →recent activity