Block #73,324,399

← previous blocknext block →recent activity

Analyzing

Block #73,324,399

18 transactions · 13 stateful · 2026-05-08 21:42:59 UTC

Parallelism

89/100

Blocked

31%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,399  ·  18 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

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe1593239…2180

0x065c9d…c394

3 touches
1 conflict

0x48914365…11fe

0x065c9d…c394

2 touches
0 conflicts

0xab4b6c67…fde9

0x065c9d…c394

2 touches
0 conflicts

0xd41467cf…4f0e

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: 0x34b6552d…112a6f

1 conflict on slot 0xb389d45f2b…a98a4c

← previous block·next block →recent activity