Block #72,296,580

← previous blocknext block →recent activity

Analyzing

Block #72,296,580

14 transactions · 12 stateful · 2026-05-04 03:38:10 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xa2a78c06…344a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2f6f3587…7be7

0x065c9d…c394

3 touches
1 conflict

0x59e6fe56…6ec0

0x065c9d…c394

3 touches
1 conflict

0x7213acb3…f04c

0x065c9d…c394

2 touches
0 conflicts

0x8437e96b…fe65

0x065c9d…c394

2 touches
0 conflicts

0xac8df0a0…6818

0x065c9d…c394

2 touches
0 conflicts

0xc27b1679…33af

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 0xa2a78c064f…3c344a

← previous block·next block →recent activity