Block #73,360,432

← previous blocknext block →recent activity

Analyzing

Block #73,360,432

10 transactions · 8 stateful · 2026-05-09 01:42:33 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,360,432  ·  10 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

0x81b21084…c893

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x971bbb3b…baac

0x065c9d…c394

3 touches
1 conflict

0x5aa24f04…5af6

0x065c9d…c394

2 touches
0 conflicts

0x6b9999de…cf58

0x065c9d…c394

2 touches
0 conflicts

0x8ebcfa07…a5ed

0x065c9d…c394

2 touches
0 conflicts

0x9f5a87f4…f821

0x065c9d…c394

2 touches
0 conflicts

0xd858ae86…004e

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 0x81b2108464…6bc893

← previous block·next block →recent activity