Block #72,288,285

← previous blocknext block →recent activity

Analyzing

Block #72,288,285

14 transactions · 11 stateful · 2026-05-04 02:42:31 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,288,285  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x71a9923d…ff06

0x34b655…2a6f

4 touches
1 conflict

0x7cd9fd28…a158

0x34b655…2a6f

4 touches
1 conflict

0x88915805…fbc9

0x34b655…2a6f

4 touches
1 conflict

0xb5d1cad9…40b0

0x34b655…2a6f

4 touches
1 conflict

0xbe9d1d23…3de2

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity