Block #72,496,785

← previous blocknext block →recent activity

Analyzing

Block #72,496,785

10 transactions · 9 stateful · 2026-05-05 01:51:51 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x9f1a3707…b515

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3fc8ed07…d43a

0x065c9d…c394

4 touches
1 conflict

0x26827594…19dd

0x065c9d…c394

3 touches
1 conflict

0x80f200aa…7dcf

0x065c9d…c394

3 touches
1 conflict

0x4efdf106…980b

0x065c9d…c394

3 touches
1 conflict

0x693309f9…226e

0x065c9d…c394

3 touches
1 conflict

0xffe431af…8faa

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 0x9f1a370739…2eb515

← previous block·next block →recent activity