Block #73,503,839

← previous blocknext block →recent activity

Analyzing

Block #73,503,839

17 transactions · 16 stateful · 2026-05-09 17:37:01 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,503,839  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x684f765a…5a0a

0x065c9d…c394

3 touches
1 conflict

0xb646c825…7f35

0x065c9d…c394

3 touches
1 conflict

0x5d09cf28…7def

0x0c65a0…0852

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity