Block #72,226,304

← previous blocknext block →recent activity

Analyzing

Block #72,226,304

5 transactions · 5 stateful · 2026-05-03 19:45:54 UTC

Parallelism

60/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,226,304  ·  5 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

0x14ede7a0…8409

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0fb888a2…a7b0

0x065c9d…c394

3 touches
1 conflict

0x8740793c…e07c

0x065c9d…c394

3 touches
1 conflict

0x22293d4e…b01a

0x065c9d…c394

2 touches
0 conflicts

0x298bcc29…3960

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x4886c242…4985

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

1 conflict on slot 0x14ede7a0aa…a58409

← previous block·next block →recent activity