Block #72,301,120

← previous blocknext block →recent activity

Analyzing

Block #72,301,120

14 transactions · 13 stateful · 2026-05-04 04:08:26 UTC

Parallelism

64/100

Blocked

31%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,301,120  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb5ef94d0…7b36

0x065c9d…c394

4 touches
1 conflict

0x415463a3…9953

0x065c9d…c394

3 touches
1 conflict

0x522252d3…dea4

0x34b655…2a6f

2 touches
0 conflicts

0x58799a46…7030

0x34b655…2a6f

2 touches
0 conflicts

0x5da6e2fe…021e

0x34b655…2a6f

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

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity