Block #72,429,605

← previous blocknext block →recent activity

Analyzing

Block #72,429,605

11 transactions · 9 stateful · 2026-05-04 18:24:27 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1fe379d0…c575

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7e438c85…f897

0x065c9d…c394

4 touches
1 conflict

0x77834fd2…44b4

0x065c9d…c394

2 touches
0 conflicts

0xa480e389…ff4a

0x065c9d…c394

2 touches
0 conflicts

0xab46ab52…e609

0x065c9d…c394

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

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 0x0000000000…00003d

← previous block·next block →recent activity