Block #72,288,314

← previous blocknext block →recent activity

Analyzing

Block #72,288,314

18 transactions · 14 stateful · 2026-05-04 02:42:42 UTC

Parallelism

89/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,288,314  ·  18 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

0xb378025c…30cf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3eadb0b6…d2f7

0x34b655…2a6f

4 touches
1 conflict

0x578e7f66…1b56

0x34b655…2a6f

4 touches
1 conflict

0x6d0c65d9…c36f

0x34b655…2a6f

4 touches
1 conflict

0xb57f7d3a…b533

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21bf

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 0xb378025c92…8630cf

← previous block·next block →recent activity