Block #72,400,070

← previous blocknext block →recent activity

Analyzing

Block #72,400,070

36 transactions · 28 stateful · 2026-05-04 15:07:41 UTC

Parallelism

75/100

Blocked

79%

Avg conflicts / tx

2.33

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,400,070  ·  36 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x00000000…0002

0x7e9d3a…9fda

14 touches
21 conflicts

0xec1d6663…6042

0x34b655…2a6f

14 touches
21 conflicts

0x1c268526…53c1

0x34b655…2a6f

12 touches
15 conflicts

0x8571fbdb…345a

0x34b655…2a6f

12 touches
15 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

10 touches
10 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

10 touches
10 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

10 touches
10 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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity