Block #73,500,332

← previous blocknext block →recent activity

Analyzing

Block #73,500,332

14 transactions · 11 stateful · 2026-05-09 17:13:36 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,500,332  ·  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

0xd976d098…ae1d

0x34b655…2a6f

10 touches
10 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

10 touches
10 conflicts

0x578e7f66…1b56

0x34b655…2a6f

8 touches
6 conflicts

0x5d563cc8…e73e

0x34b655…2a6f

8 touches
6 conflicts

0x5d70606a…1d53

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x64e30b79…bc29

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

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 0xd976d09817…2fae1d

← previous block·next block →recent activity