Block #72,496,734

← previous blocknext block →recent activity

Analyzing

Block #72,496,734

7 transactions · 5 stateful · 2026-05-05 01:51:30 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,734  ·  7 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

0xfcca00c5…fec1

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa2f07d9e…86c7

0x065c9d…c394

3 touches
1 conflict

0x72c9788c…1334

0x065c9d…c394

3 touches
1 conflict

0x56caf1b9…3d81

0x065c9d…c394

2 touches
0 conflicts

0x89292a99…c90e

0x065c9d…c394

2 touches
0 conflicts

0xac4eb456…7ad4

0x065c9d…c394

2 touches
0 conflicts

0xfcd881b4…089d

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 0xfcca00c5b1…81fec1

← previous block·next block →recent activity