Block #72,394,770

← previous blocknext block →recent activity

Analyzing

Block #72,394,770

8 transactions · 8 stateful · 2026-05-04 14:32:21 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,394,770  ·  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

0x1a64fc11…76d7

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0e0b4515…578c

0x065c9d…c394

4 touches
1 conflict

0xde9b9ecd…4daf

0x065c9d…c394

3 touches
1 conflict

0x8f2965b1…e024

0x065c9d…c394

3 touches
1 conflict

0x8fbc915c…96d7

0x065c9d…c394

3 touches
1 conflict

0xab8abb88…3d49

0x065c9d…c394

3 touches
1 conflict

0xed2d342e…1562

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 0x1a64fc11df…d976d7

← previous block·next block →recent activity