Block #72,399,465

← previous blocknext block →recent activity

Analyzing

Block #72,399,465

20 transactions · 17 stateful · 2026-05-04 15:03:39 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,399,465  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x7e9d3a…9fda

6 touches
3 conflicts

0x124b03a9…519a

0xd32edf…ff58

5 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x94eb44ef…e44d

0x065c9d…c394

4 touches
1 conflict

0xc1f6af8e…6659

0x065c9d…c394

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity