Block #72,571,353

← previous blocknext block →recent activity

Analyzing

Block #72,571,353

11 transactions · 9 stateful · 2026-05-05 10:08:19 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,571,353  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x62c421a8…7c34

0x065c9d…c394

4 touches
1 conflict

0x68c4da1d…d7c8

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x276899cd…6aaf

0x065c9d…c394

3 touches
1 conflict

0xa369abd4…7c25

0x065c9d…c394

3 touches
1 conflict

0xa528bcb8…ba67

0x065c9d…c394

3 touches
1 conflict

0xee825dc2…c25b

0x065c9d…c394

3 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity