Block #72,284,599

← previous blocknext block →recent activity

Analyzing

Block #72,284,599

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

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,284,599  ·  10 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

0x1d49c95a…9780

0x065c9d…c394

4 touches
1 conflict

0xfd9bd05d…3012

0x065c9d…c394

3 touches
1 conflict

0xca11887b…4061

0x065c9d…c394

3 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x005fb969…2d97

0x34b655…2a6f

2 touches
0 conflicts

0x1279ee2d…ae99

0x34b655…2a6f

2 touches
0 conflicts

0x157d1e46…85f6

0x34b655…2a6f

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 0x1d49c95ace…549780

← previous block·next block →recent activity