Block #73,387,460

← previous blocknext block →recent activity

Analyzing

Block #73,387,460

13 transactions · 10 stateful · 2026-05-09 04:42:24 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,387,460  ·  13 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

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xb9edf2e4…f283

0x065c9d…c394

3 touches
1 conflict

0x6f2f6387…f0ee

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0ea0d8ad…def6

0x065c9d…c394

2 touches
0 conflicts

0x15458397…7890

0x065c9d…c394

2 touches
0 conflicts

0xaba42265…0e62

0x065c9d…c394

2 touches
0 conflicts

0xbfec9e66…6c5a

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: 0x065c9d28…a9c394

1 conflict on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity