Block #72,314,559

← previous blocknext block →recent activity

Analyzing

Block #72,314,559

6 transactions · 5 stateful · 2026-05-04 05:37:56 UTC

Parallelism

50/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,314,559  ·  6 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

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x911aef96…5e2c

0x065c9d…c394

2 touches
0 conflicts

0xa5c2f99f…9d4e

0x065c9d…c394

2 touches
0 conflicts

0xda0a2ab6…fd3a

0x065c9d…c394

2 touches
0 conflicts

0xe1b81ed6…3ddb

0x065c9d…c394

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

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 0xbbee74c2e7…6e567a

← previous block·next block →recent activity