Block #72,221,296

← previous blocknext block →recent activity

Analyzing

Block #72,221,296

7 transactions · 6 stateful · 2026-05-03 19:12:21 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,221,296  ·  7 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

0xea7f2e45…f6f2

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x50e62872…373f

0x065c9d…c394

3 touches
1 conflict

0x7a990e31…0839

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x9f56afc7…418b

0x065c9d…c394

2 touches
0 conflicts

0xa9838c09…7ecd

0x065c9d…c394

2 touches
0 conflicts

0xccdad362…7972

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 0xea7f2e45a2…50f6f2

← previous block·next block →recent activity