Block #72,314,525

← previous blocknext block →recent activity

Analyzing

Block #72,314,525

10 transactions · 9 stateful · 2026-05-04 05:37:43 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,314,525  ·  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

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x18071fc2…629c

0x065c9d…c394

3 touches
1 conflict

0x1b2c8196…48fc

0x065c9d…c394

3 touches
1 conflict

0x663c86e9…d6fb

0x065c9d…c394

3 touches
1 conflict

0xdc30ea0c…a2ef

0x065c9d…c394

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

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 0x24968e6db4…f00132

← previous block·next block →recent activity