Block #72,429,931

← previous blocknext block →recent activity

Analyzing

Block #72,429,931

17 transactions · 15 stateful · 2026-05-04 18:26:37 UTC

Parallelism

59/100

Blocked

40%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,429,931  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

12 touches
15 conflicts

0x220f4f84…15f8

0x34b655…2a6f

10 touches
10 conflicts

0xe072d43a…1835

0x34b655…2a6f

10 touches
10 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8af5021b…6256

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

15 conflicts on slot 0xf853eb8e72…d84027

← previous block·next block →recent activity