Block #73,381,732

← previous blocknext block →recent activity

Analyzing

Block #73,381,732

36 transactions · 30 stateful · 2026-05-09 04:04:16 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

2.25

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,381,732  ·  36 txs across 13 waves  ·  depth 13
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

wave w12

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

0x4b99c6e5…3051

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

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…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

55 conflicts on slot 0x4b99c6e5cb…b63051

← previous block·next block →recent activity