Block #72,430,770

← previous blocknext block →recent activity

Analyzing

Block #72,430,770

21 transactions · 18 stateful · 2026-05-04 18:32:13 UTC

Parallelism

76/100

Blocked

61%

Avg conflicts / tx

1.05

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,430,770  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x5c8c6ab6…dc36

0x065c9d…c394

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x2343b4c2…d6bb

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x65e795ca…0320

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

10 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity