Block #73,597,670

← previous blocknext block →recent activity

Analyzing

Block #73,597,670

15 transactions · 14 stateful · 2026-05-10 04:00:27 UTC

Parallelism

60/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,597,670  ·  15 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

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x90d24713…b88a

0x1b6862…e19c

10 touches
10 conflicts

0xbc77e6ad…f695

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x46027744…9629

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0x1b68626d…2de19c

10 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity