Block #72,301,346

← previous blocknext block →recent activity

Analyzing

Block #72,301,346

11 transactions · 9 stateful · 2026-05-04 04:09:56 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,346  ·  11 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

0xe4653696…8441

0x065c9d…c394

4 touches
1 conflict

0xf5dc4bbf…c7ba

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1bf14693…8f13

0x065c9d…c394

4 touches
1 conflict

0x4b2e3451…da37

0x065c9d…c394

3 touches
1 conflict

0x2afee649…9ae5

0x065c9d…c394

3 touches
1 conflict

0x3ba67c82…3245

0x065c9d…c394

3 touches
1 conflict

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 0xe4653696a4…c48441

← previous block·next block →recent activity