Block #72,213,457

← previous blocknext block →recent activity

Analyzing

Block #72,213,457

29 transactions · 24 stateful · 2026-05-03 18:19:39 UTC

Parallelism

76/100

Blocked

67%

Avg conflicts / tx

1.69

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,213,457  ·  29 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

12 touches
15 conflicts

0x00000000…0002

0x7e9d3a…9fda

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe429e4c9…9510

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

8 touches
6 conflicts

0x9b8800c1…ed12

0x34b655…2a6f

8 touches
6 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity