Block #72,430,004

← previous blocknext block →recent activity

Analyzing

Block #72,430,004

8 transactions · 7 stateful · 2026-05-04 18:27:06 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,004  ·  8 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

0x83ffc773…efbf

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x02bfdbf9…6514

0x34b655…2a6f

4 touches
1 conflict

0x09a1a0e6…3eab

0x065c9d…c394

4 touches
1 conflict

0x25de453d…9573

0x34b655…2a6f

2 touches
0 conflicts

0x2aa8d413…a1fa

0x34b655…2a6f

2 touches
0 conflicts

0x4289c33f…f0a5

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: 0x065c9d28…a9c394

1 conflict on slot 0x83ffc77359…ebefbf

← previous block·next block →recent activity