Block #73,390,123

← previous blocknext block →recent activity

Analyzing

Block #73,390,123

11 transactions · 9 stateful · 2026-05-09 05:00:07 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,390,123  ·  11 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

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x6dafbc6f…8711

0x065c9d…c394

2 touches
0 conflicts

0x9881ad02…c68f

0x065c9d…c394

2 touches
0 conflicts

0xb11b6d79…8dd1

0x065c9d…c394

2 touches
0 conflicts

0xb1a31f91…6648

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x4d87512b00…43897c

← previous block·next block →recent activity