Block #72,233,621

← previous blocknext block →recent activity

Analyzing

Block #72,233,621

23 transactions · 17 stateful · 2026-05-03 20:35:06 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,233,621  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x50c2960c…5f37

0x34b655…2a6f

8 touches
6 conflicts

0x00f245ce…1e10

0x34b655…2a6f

8 touches
6 conflicts

0x35b85d8e…1edd

0x34b655…2a6f

8 touches
6 conflicts

0xaf498679…7732

0x34b655…2a6f

8 touches
6 conflicts

0xcd5c7f64…ad4b

0x34b655…2a6f

8 touches
6 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity