Block #73,495,385

← previous blocknext block →recent activity

Analyzing

Block #73,495,385

33 transactions · 24 stateful · 2026-05-09 16:40:38 UTC

Parallelism

79/100

Blocked

63%

Avg conflicts / tx

1.03

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,495,385  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0x849f3e33…c095

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xfbbc35e2…f66b

0x34b655…2a6f

6 touches
3 conflicts

0x7cab84dd…a441

0x34b655…2a6f

6 touches
3 conflicts

0x118380dc…d354

0xd32edf…ff58

5 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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity