Block #73,396,704

← previous blocknext block →recent activity

Analyzing

Block #73,396,704

14 transactions · 12 stateful · 2026-05-09 05:43:57 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,396,704  ·  14 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

0xfc20d5de…6e55

0x065c9d…c394

4 touches
1 conflict

0x0620684b…473b

0x065c9d…c394

3 touches
1 conflict

0x7a66bce1…64cd

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0xe24cf94f…f7da

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

2 touches
0 conflicts

0xfbe161dd…757b

0x3bd359…433a

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 0xfc20d5dee2…5a6e55

← previous block·next block →recent activity