Block #72,271,721

← previous blocknext block →recent activity

Analyzing

Block #72,271,721

7 transactions · 6 stateful · 2026-05-04 00:51:10 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,271,721  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

4 touches
1 conflict

0x1608635c…d25d

0x34b655…2a6f

4 touches
1 conflict

0x6f5888a2…7a36

0x34b655…2a6f

2 touches
0 conflicts

0x79347b24…9fba

0x34b655…2a6f

2 touches
0 conflicts

0x81716ce9…095f

0x34b655…2a6f

2 touches
0 conflicts

0x95e5ee51…5e3e

0x34b655…2a6f

2 touches
0 conflicts

0xa4c6da38…3a6a

0x34b655…2a6f

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity