Block #73,389,290

← previous blocknext block →recent activity

Analyzing

Block #73,389,290

24 transactions · 16 stateful · 2026-05-09 04:54:33 UTC

Parallelism

75/100

Blocked

31%

Avg conflicts / tx

0.46

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,389,290  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xac0935cf…ca70

0xd32edf…ff58

7 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xe038916c…b1be

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x4c3e9653…ba35

0x065c9d…c394

4 touches
1 conflict

0xea46619e…10ad

0x065c9d…c394

3 touches
1 conflict

0xdf4ed324…f43b

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

6 conflicts on slot 0xac0935cf1f…fcca70

← previous block·next block →recent activity