Block #73,389,525

← previous blocknext block →recent activity

Analyzing

Block #73,389,525

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

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,389,525  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x1ad6054b…178e

0x065c9d…c394

2 touches
0 conflicts

0x1f3e7a45…3894

0x065c9d…c394

2 touches
0 conflicts

0x4708fdde…3514

0x065c9d…c394

2 touches
0 conflicts

0x8227deb9…9922

0x065c9d…c394

2 touches
0 conflicts

0xa3a29de9…11a2

0x065c9d…c394

2 touches
0 conflicts

0xae68453f…8139

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity