Block #72,283,649

← previous blocknext block →recent activity

Analyzing

Block #72,283,649

23 transactions · 20 stateful · 2026-05-04 02:11:20 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.87

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,649  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x9bd2f300…b62a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x49339736…b223

0x34b655…2a6f

6 touches
3 conflicts

0x91ca1434…4017

0x34b655…2a6f

6 touches
3 conflicts

0x893cd52c…5766

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity