Block #73,386,819

← previous blocknext block →recent activity

Analyzing

Block #73,386,819

14 transactions · 10 stateful · 2026-05-09 04:38:08 UTC

Parallelism

86/100

Blocked

10%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,386,819  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa088f9af…5c49

0x065c9d…c394

4 touches
1 conflict

0x6fa7f027…cb8c

0x065c9d…c394

3 touches
1 conflict

0x08b9e8bc…47c8

0x065c9d…c394

2 touches
0 conflicts

0x0d43c588…54a3

0x065c9d…c394

2 touches
0 conflicts

0x6766e944…21f8

0x065c9d…c394

2 touches
0 conflicts

0x7295dada…3824

0x065c9d…c394

2 touches
0 conflicts

0xf5b22dbf…6c07

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 0x0000000000…00003d

← previous block·next block →recent activity