Block #73,648,299

← previous blocknext block →recent activity

Analyzing

Block #73,648,299

16 transactions · 13 stateful · 2026-05-10 09:39:43 UTC

Parallelism

88/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,648,299  ·  16 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

0x889b6f56…5c1b

0x065c9d…c394

4 touches
1 conflict

0xa6ecd0b9…505d

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x50997ada…364d

0x6c4bfa…a540

4 touches
1 conflict

0xe94e77ab…f017

0x6c4bfa…a540

4 touches
1 conflict

0xf0f673fd…37a7

0x6c4bfa…a540

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

1 conflict on slot 0x889b6f5604…aa5c1b

← previous block·next block →recent activity