Block #72,429,668

← previous blocknext block →recent activity

Analyzing

Block #72,429,668

14 transactions · 10 stateful · 2026-05-04 18:24:52 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,429,668  ·  14 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0x6423fcab…a7c1

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0xe1fd24a0…eaa6

0x34b655…2a6f

6 touches
3 conflicts

0xeb0915f1…c150

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity