Block #73,594,252

← previous blocknext block →recent activity

Analyzing

Block #73,594,252

25 transactions · 21 stateful · 2026-05-10 03:37:42 UTC

Parallelism

76/100

Blocked

57%

Avg conflicts / tx

1.32

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,594,252  ·  25 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

0x8240d70c…7c3b

0x34b655…2a6f

10 touches
10 conflicts

0x848152a3…1c8e

0xd32edf…ff58

9 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

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 0x8240d70c8a…f27c3b

← previous block·next block →recent activity