Block #73,660,624

← previous blocknext block →recent activity

Analyzing

Block #73,660,624

37 transactions · 30 stateful · 2026-05-10 11:02:44 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

1.43

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,660,624  ·  37 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3bb44ad6…96fd

0xd32edf…ff58

15 touches
28 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0x14845934…d13c

0x34b655…2a6f

8 touches
6 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xba5743c7…21c3

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

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: 0xd32edf66…9fff58

28 conflicts on slot 0x3bb44ad6dd…a796fd

← previous block·next block →recent activity