Block #73,480,641

← previous blocknext block →recent activity

Analyzing

Block #73,480,641

14 transactions · 13 stateful · 2026-05-09 15:02:30 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,480,641  ·  14 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

0x64e30b79…bc29

0x34b655…2a6f

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0x908d4442…2c4b

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x1acaa26f…7b77

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

10 conflicts on slot 0x64e30b7938…efbc29

← previous block·next block →recent activity