Block #72,429,963

← previous blocknext block →recent activity

Analyzing

Block #72,429,963

26 transactions · 21 stateful · 2026-05-04 18:26:50 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,429,963  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0xcb2dc2cb…a9e9

0x34b655…2a6f

6 touches
3 conflicts

0xddf0e471…ce9d

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

6 touches
3 conflicts

0x00f245ce…1e10

0x34b655…2a6f

6 touches
3 conflicts

0x02bfdbf9…6514

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity