Block #72,429,541

← previous blocknext block →recent activity

Analyzing

Block #72,429,541

28 transactions · 20 stateful · 2026-05-04 18:24:01 UTC

Parallelism

61/100

Blocked

60%

Avg conflicts / tx

1.61

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,429,541  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x01ce8503…f81e

0xd32edf…ff58

17 touches
36 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xf35dca9e…bd8b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xcc709e32…0e0b

0x065c9d…c394

5 touches
3 conflicts

0xd9f18d9a…141d

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: 0xd32edf66…9fff58

36 conflicts on slot 0x01ce8503c1…bff81e

← previous block·next block →recent activity