Block #72,572,512

← previous blocknext block →recent activity

Analyzing

Block #72,572,512

10 transactions · 9 stateful · 2026-05-05 10:16:03 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,572,512  ·  10 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

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x334bbdc1…4748

0x065c9d…c394

4 touches
1 conflict

0x3b211491…054d

0x065c9d…c394

3 touches
1 conflict

0x1159c47b…53b2

0x065c9d…c394

2 touches
0 conflicts

0x1c4dde4b…de28

0x065c9d…c394

2 touches
0 conflicts

0x5e72274f…d7f3

0x065c9d…c394

2 touches
0 conflicts

0x80ffd9b0…071c

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 0xbbee74c2e7…6e567a

← previous block·next block →recent activity