Block #72,429,601

← previous blocknext block →recent activity

Analyzing

Block #72,429,601

5 transactions · 3 stateful · 2026-05-04 18:24:25 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,429,601  ·  5 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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x5d14bf75…3df2

0x065c9d…c394

4 touches
1 conflict

0x61ccf4be…e954

0x065c9d…c394

3 touches
1 conflict

0x364ecc37…679b

0x065c9d…c394

3 touches
1 conflict

0x161f1e59…4b97

0x065c9d…c394

3 touches
1 conflict

0xb9adf07e…02c4

0x065c9d…c394

2 touches
0 conflicts

0xd4540adc…801c

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 0xffe431af56…838faa

← previous block·next block →recent activity