Block #73,210,624

← previous blocknext block →recent activity

Analyzing

Block #73,210,624

9 transactions · 7 stateful · 2026-05-08 09:06:04 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,210,624  ·  9 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x5939acf5…179f

0x96b79e…d00a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8bcd90e8…5673

0x065c9d…c394

2 touches
0 conflicts

0x490911cc…5fea

0x0c65a0…0852

2 touches
0 conflicts

0x8214d58e…3991

0x0c65a0…0852

2 touches
0 conflicts

0x5860c4f3…0c39

0x3bd359…433a

2 touches
0 conflicts

0x5584a2e5…e2c2

0x96b79e…d00a

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity