← previous blocknext block →recent activity

Analyzing

Block #73,383,422

11 transactions · 10 stateful · 2026-05-09 04:15:31 UTC

Parallelism

73/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x0ad45121…0492

0x065c9d…c394

2 touches
0 conflicts

0x5be50ac3…4b6b

0x065c9d…c394

2 touches
0 conflicts

0x669a6f8b…ba3a

0x065c9d…c394

2 touches
0 conflicts

0x7f81fb82…633e

0x065c9d…c394

2 touches
0 conflicts

0xf6b5c774…12de

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x438cf5f603…8ef077

← previous block·next block →recent activity