Block #72,301,232

← previous blocknext block →recent activity

Analyzing

Block #72,301,232

7 transactions · 6 stateful · 2026-05-04 04:09: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,301,232  ·  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

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x135c6862…9eb6

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

2 touches
0 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity