Block #72,498,329

← previous blocknext block →recent activity

Analyzing

Block #72,498,329

8 transactions · 6 stateful · 2026-05-05 02:02:08 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,498,329  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0b65a681…4e51

0x065c9d…c394

2 touches
0 conflicts

0x286fd7f0…7592

0x065c9d…c394

2 touches
0 conflicts

0x34180922…5dc1

0x065c9d…c394

2 touches
0 conflicts

0xb8c3e87f…2e99

0x065c9d…c394

2 touches
0 conflicts

0xb9fe4e27…3208

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity