← previous blocknext block →recent activity

Analyzing

Block #73,597,491

8 transactions · 7 stateful · 2026-05-10 03:59:15 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,597,491  ·  8 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

0x60b5fa43…af29

0x065c9d…c394

4 touches
1 conflict

0x8e9c6582…d9e1

0x065c9d…c394

4 touches
1 conflict

0xe7c6ca99…9acb

0x065c9d…c394

3 touches
1 conflict

0x032ea6ca…c736

0x065c9d…c394

3 touches
1 conflict

0x06cd9c92…c074

0x065c9d…c394

3 touches
1 conflict

0x9f5a332f…ea92

0x065c9d…c394

3 touches
1 conflict

0x6a820c51…5917

0x34b655…2a6f

2 touches
0 conflicts

0x803cc4fb…c31b

0x34b655…2a6f

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 0x60b5fa4356…81af29

← previous block·next block →recent activity