Block #72,859,566

← previous blocknext block →recent activity

Analyzing

Block #72,859,566

25 transactions · 19 stateful · 2026-05-06 18:09:50 UTC

Parallelism

72/100

Blocked

63%

Avg conflicts / tx

1.28

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,859,566  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xa44972ad…f8e8

0xd32edf…ff58

7 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x499adbcf…eb20

0x34b655…2a6f

6 touches
3 conflicts

0xe72962f6…e169

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

5 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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity