Block #72,425,801

← previous blocknext block →recent activity

Analyzing

Block #72,425,801

7 transactions · 6 stateful · 2026-05-04 17:59:10 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x1c6f8b9b…8068

0x065c9d…c394

2 touches
0 conflicts

0x2232d161…0202

0x065c9d…c394

2 touches
0 conflicts

0x26932743…e11e

0x065c9d…c394

2 touches
0 conflicts

0x3258ac13…a315

0x065c9d…c394

2 touches
0 conflicts

0x6c6b2630…ddb3

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity