Block #72,283,451

← previous blocknext block →recent activity

Analyzing

Block #72,283,451

18 transactions · 11 stateful · 2026-05-04 02:10:00 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,283,451  ·  18 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x88915805…fbc9

0x34b655…2a6f

8 touches
6 conflicts

0x53c41998…7d52

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd6a0a7b8…fb34

0x34b655…2a6f

6 touches
3 conflicts

0xe4af4c87…9964

0x34b655…2a6f

6 touches
3 conflicts

0xfbabb02d…af07

0x34b655…2a6f

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

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