Block #73,660,649

← previous blocknext block →recent activity

Analyzing

Block #73,660,649

23 transactions · 18 stateful · 2026-05-10 11:02:55 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,660,649  ·  23 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

0xfc0c05f6…3523

0xd32edf…ff58

5 touches
3 conflicts

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x3ded8a5b…3cf0

0x34b655…2a6f

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0x6fb51aa5…def2

0x065c9d…c394

3 touches
1 conflict

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: 0xd32edf66…9fff58

3 conflicts on slot 0xfc0c05f6c9…203523

← previous block·next block →recent activity