Block #73,383,014

← previous blocknext block →recent activity

Analyzing

Block #73,383,014

10 transactions · 9 stateful · 2026-05-09 04:12:48 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,383,014  ·  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

0x7be98311…ba68

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0a0c1e42…ff06

0x065c9d…c394

3 touches
1 conflict

0xf131510a…441a

0x065c9d…c394

3 touches
1 conflict

0x8728cf1c…4751

0x065c9d…c394

2 touches
0 conflicts

0x889b6f56…5c1b

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

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 0x7be983117b…22ba68

← previous block·next block →recent activity