Block #73,506,973

← previous blocknext block →recent activity

Analyzing

Block #73,506,973

13 transactions · 12 stateful · 2026-05-09 17:57:56 UTC

Parallelism

62/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,506,973  ·  13 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…003d

0x065c9d…c394

8 touches
6 conflicts

0x0175b7a6…1dbc

0x6c4bfa…a540

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6c4bfa…a540

4 touches
1 conflict

0x5b3dfef8…a676

0x6c4bfa…a540

4 touches
1 conflict

0xaa03918c…f1c7

0x6c4bfa…a540

4 touches
1 conflict

0xc5564f8e…f4bf

0x6c4bfa…a540

4 touches
1 conflict

0xed57bddf…1abf

0xc8689a…ee79

4 touches
1 conflict

0xd44f1117…1b33

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity