Block #72,399,361

← previous blocknext block →recent activity

Analyzing

Block #72,399,361

33 transactions · 22 stateful · 2026-05-04 15:02:57 UTC

Parallelism

82/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,399,361  ·  33 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xd434422b…e717

0x34b655…2a6f

6 touches
3 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0x4f483049…3cc7

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0xbd2e678d…00ad

0xd32edf…ff58

5 touches
3 conflicts

0x14d1bf0e…e09b

0x1b6862…e19c

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