Block #72,395,051

← previous blocknext block →recent activity

Analyzing

Block #72,395,051

22 transactions · 19 stateful · 2026-05-04 14:34:13 UTC

Parallelism

73/100

Blocked

68%

Avg conflicts / tx

1.36

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,395,051  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0002

0x7e9d3a…9fda

10 touches
10 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

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