Block #72,310,150

← previous blocknext block →recent activity

Analyzing

Block #72,310,150

29 transactions · 27 stateful · 2026-05-04 05:08:36 UTC

Parallelism

79/100

Blocked

63%

Avg conflicts / tx

1.38

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,310,150  ·  29 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

0x9d1c9977…994d

0xd32edf…ff58

11 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x21d8e673…067a

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

15 conflicts on slot 0x9d1c997711…c9994d

← previous block·next block →recent activity