Block #72,576,320

← previous blocknext block →recent activity

Analyzing

Block #72,576,320

7 transactions · 6 stateful · 2026-05-05 10:41:26 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,576,320  ·  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

0x8d0b2e09…dedc

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x05ea9a04…e102

0x065c9d…c394

3 touches
1 conflict

0x7fbb19a1…3968

0x065c9d…c394

3 touches
1 conflict

0x22acc598…60ba

0x065c9d…c394

2 touches
0 conflicts

0x2903dafc…45f4

0x065c9d…c394

2 touches
0 conflicts

0x3da11c10…aa48

0x065c9d…c394

2 touches
0 conflicts

0x9c99e0f6…9e10

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 0x8d0b2e09e4…28dedc

← previous block·next block →recent activity