Block #73,501,008

← previous blocknext block →recent activity

Analyzing

Block #73,501,008

24 transactions · 18 stateful · 2026-05-09 17:18:06 UTC

Parallelism

79/100

Blocked

67%

Avg conflicts / tx

1.08

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,501,008  ·  24 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

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0xd976d098…ae1d

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0x5728edaf…f1d4

0x34b655…2a6f

6 touches
3 conflicts

0x578e7f66…1b56

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

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 0xa91c899f02…fa6ee3

← previous block·next block →recent activity