Block #72,314,734

← previous blocknext block →recent activity

Analyzing

Block #72,314,734

20 transactions · 17 stateful · 2026-05-04 05:39:06 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,314,734  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x05e01646…bf1f

0xd32edf…ff58

7 touches
6 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x6aa624fd…a84c

0x1b6862…e19c

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

6 touches
3 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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity