Block #72,296,304

← previous blocknext block →recent activity

Analyzing

Block #72,296,304

14 transactions · 12 stateful · 2026-05-04 03:36:20 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,304  ·  14 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

0xc166a323…1f33

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x75f928fc…0465

0x34b655…2a6f

4 touches
1 conflict

0x5d7f7587…6e7c

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0028

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 0xc166a323cb…201f33

← previous block·next block →recent activity