Block #73,374,949

← previous blocknext block →recent activity

Analyzing

Block #73,374,949

35 transactions · 23 stateful · 2026-05-09 03:19:12 UTC

Parallelism

66/100

Blocked

70%

Avg conflicts / tx

2.14

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,374,949  ·  35 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

0xf256472c…aa70

0xd32edf…ff58

23 touches
66 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0x511f46a7…edae

0x1b6862…e19c

6 touches
3 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x659bd0…a9da

6 touches
3 conflicts

0x00000000…0002

0x659bd0…a9da

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

66 conflicts on slot 0xf256472c40…dbaa70

← previous block·next block →recent activity