Block #73,399,708

← previous blocknext block →recent activity

Analyzing

Block #73,399,708

12 transactions · 11 stateful · 2026-05-09 06:04:01 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,399,708  ·  12 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

0x031569a0…40db

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x0277cd8d…e2f2

0x065c9d…c394

3 touches
1 conflict

0x9b675023…d916

0x065c9d…c394

2 touches
0 conflicts

0xac8b46fb…688f

0x065c9d…c394

2 touches
0 conflicts

0xb944d31e…61c2

0x065c9d…c394

2 touches
0 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

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 0x031569a043…d940db

← previous block·next block →recent activity