Block #73,389,289

← previous blocknext block →recent activity

Analyzing

Block #73,389,289

36 transactions · 20 stateful · 2026-05-09 04:54:33 UTC

Parallelism

67/100

Blocked

65%

Avg conflicts / tx

1.89

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,389,289  ·  36 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x0736d2b6…ac30

0xd32edf…ff58

23 touches
66 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xe483d4e3…e531

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

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

66 conflicts on slot 0x0736d2b6bb…5cac30

← previous block·next block →recent activity