Block #72,425,938

← previous blocknext block →recent activity

Analyzing

Block #72,425,938

11 transactions · 8 stateful · 2026-05-04 18:00:05 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,425,938  ·  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

0x117de85e…838b

0x065c9d…c394

4 touches
1 conflict

0x34471014…7658

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x03d109e4…5f1f

0x065c9d…c394

3 touches
1 conflict

0xd4b8b752…4344

0x065c9d…c394

3 touches
1 conflict

0x228021fa…ac13

0x065c9d…c394

3 touches
1 conflict

0xeb7f5416…1b43

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

← previous block·next block →recent activity