Block #72,430,556

← previous blocknext block →recent activity

Analyzing

Block #72,430,556

5 transactions · 4 stateful · 2026-05-04 18:30:47 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,556  ·  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

0xb96a4937…d4b5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x15e84fe2…b3eb

0x065c9d…c394

3 touches
1 conflict

0x34d6e293…e4bd

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x86b4f3b9…2008

0x065c9d…c394

2 touches
0 conflicts

0x93a6a6d1…f286

0x065c9d…c394

2 touches
0 conflicts

0x97306666…b4b4

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 0xb96a493732…17d4b5

← previous block·next block →recent activity