Block #72,224,453

← previous blocknext block →recent activity

Analyzing

Block #72,224,453

14 transactions · 11 stateful · 2026-05-03 19:33:27 UTC

Parallelism

86/100

Blocked

9%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,224,453  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x453f38cd…21e0

0x065c9d…c394

4 touches
1 conflict

0x82f3519c…2a7e

0x065c9d…c394

3 touches
1 conflict

0x1450acc9…98a0

0x065c9d…c394

3 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0x17606ba6…1b6e

0x754704…b603

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity