Block #72,395,006

← previous blocknext block →recent activity

Analyzing

Block #72,395,006

23 transactions · 20 stateful · 2026-05-04 14:33:55 UTC

Parallelism

74/100

Blocked

55%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,395,006  ·  23 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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

8 touches
6 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

6 touches
3 conflicts

0xfc20ecf1…58de

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x7e9d3a…9fda

6 touches
3 conflicts

0xd39339a7…d7aa

0x065c9d…c394

5 touches
3 conflicts

0xfdd38af2…890a

0x065c9d…c394

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity