Block #73,653,335

← previous blocknext block →recent activity

Analyzing

Block #73,653,335

13 transactions · 10 stateful · 2026-05-10 10:13:36 UTC

Parallelism

62/100

Blocked

40%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,653,335  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x9a122645…a611

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x0e9bdc9b…6a11

0x065c9d…c394

4 touches
1 conflict

0x2bbc0cfb…c2be

0x1b6862…e19c

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x33321c88…b231

0x122c0d…e3fa

2 touches
0 conflicts

0x33321c88…b232

0x122c0d…e3fa

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: 0xd32edf66…9fff58

10 conflicts on slot 0x9a122645d3…5fa611

← previous block·next block →recent activity