Block #72,430,674

← previous blocknext block →recent activity

Analyzing

Block #72,430,674

5 transactions · 4 stateful · 2026-05-04 18:31:35 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,674  ·  5 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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x8ffcccd9…df64

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa8de8c71…dc40

0x065c9d…c394

3 touches
1 conflict

0x801c0f42…c161

0x065c9d…c394

3 touches
1 conflict

0x6a5c9f98…2bca

0x065c9d…c394

2 touches
0 conflicts

0x9ec24126…150e

0x065c9d…c394

2 touches
0 conflicts

0xf0912933…682f

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

1 conflict on slot 0xffe431af56…838faa

← previous block·next block →recent activity