Block #72,425,723

← previous blocknext block →recent activity

Analyzing

Block #72,425,723

20 transactions · 13 stateful · 2026-05-04 17:58:39 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,425,723  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0efceed6…843e

0xd32edf…ff58

9 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x8b7534a3…e0b5

0x188d58…ea8e

2 touches
0 conflicts

0x8b7534a3…e0b6

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001b

0x1b6862…e19c

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

10 conflicts on slot 0x0efceed649…7a843e

← previous block·next block →recent activity