Block #72,288,276

← previous blocknext block →recent activity

Analyzing

Block #72,288,276

18 transactions · 14 stateful · 2026-05-04 02:42:27 UTC

Parallelism

56/100

Blocked

57%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,288,276  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbe9d1d23…3de2

0x34b655…2a6f

6 touches
3 conflicts

0xcc6521c1…c892

0x8d66a4…3095

6 touches
3 conflicts

0xd05ff2c2…d292

0x34b655…2a6f

4 touches
1 conflict

0xe4af4c87…9964

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity