Block #72,283,153

← previous blocknext block →recent activity

Analyzing

Block #72,283,153

27 transactions · 21 stateful · 2026-05-04 02:07:59 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,283,153  ·  27 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

0xf7a382dc…125c

0xd32edf…ff58

9 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

6 touches
3 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 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 0xf7a382dc4a…74125c

← previous block·next block →recent activity