Block #73,651,522

← previous blocknext block →recent activity

Analyzing

Block #73,651,522

37 transactions · 29 stateful · 2026-05-10 10:01:24 UTC

Parallelism

65/100

Blocked

66%

Avg conflicts / tx

2.95

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,651,522  ·  37 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

0x3381ec89…030b

0xd32edf…ff58

25 touches
78 conflicts

0x17606ba6…1b6e

0x754704…b603

14 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xba5743c7…21c2

0x1b6862…e19c

10 touches
10 conflicts

0x56a919c4…ab49

0xee8c0e…1242

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

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

78 conflicts on slot 0x3381ec89bc…7b030b

← previous block·next block →recent activity