Block #73,650,377

← previous blocknext block →recent activity

Analyzing

Block #73,650,377

13 transactions · 9 stateful · 2026-05-10 09:53:42 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,650,377  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x7f81fb82…633e

0x065c9d…c394

6 touches
3 conflicts

0x9a70b151…3296

0x065c9d…c394

4 touches
1 conflict

0x69c4e699…4a31

0x065c9d…c394

3 touches
1 conflict

0xa74ec2c6…9717

0x065c9d…c394

3 touches
1 conflict

0xe0186c7f…ec47

0x065c9d…c394

3 touches
1 conflict

0x77e2108a…aedc

0x065c9d…c394

2 touches
0 conflicts

0xa2968b39…32ad

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity