Block #73,360,449

← previous blocknext block →recent activity

Analyzing

Block #73,360,449

14 transactions · 14 stateful · 2026-05-09 01:42:40 UTC

Parallelism

57/100

Blocked

43%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,360,449  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

6 touches
3 conflicts

0xd976d098…ae1d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 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 0xf853eb8e72…d84027

← previous block·next block →recent activity