Block #73,200,409

← previous blocknext block →recent activity

Analyzing

Block #73,200,409

29 transactions · 22 stateful · 2026-05-08 07:58:05 UTC

Parallelism

83/100

Blocked

50%

Avg conflicts / tx

0.66

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,200,409  ·  29 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x251861eb…78fd

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xef17b8cd…9511

0x34b655…2a6f

6 touches
3 conflicts

0x57ce49f6…bfd7

0x065c9d…c394

5 touches
3 conflicts

0x735b70e7…df03

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity