Block #72,226,463

← previous blocknext block →recent activity

Analyzing

Block #72,226,463

16 transactions · 14 stateful · 2026-05-03 19:46:58 UTC

Parallelism

81/100

Blocked

21%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,226,463  ·  16 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

0x2965e2d6…5800

0x34b655…2a6f

6 touches
3 conflicts

0xe55a330f…5b2a

0x065c9d…c394

4 touches
1 conflict

0x55328e52…30b0

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb5df4d47…2dd4

0x065c9d…c394

3 touches
1 conflict

0x54e7d2cf…c971

0x065c9d…c394

3 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x653acb35…c64f

0x065c9d…c394

2 touches
0 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

3 conflicts on slot 0x2965e2d660…395800

← previous block·next block →recent activity