Block #73,679,354

← previous blocknext block →recent activity

Analyzing

Block #73,679,354

34 transactions · 30 stateful · 2026-05-10 13:09:16 UTC

Parallelism

53/100

Blocked

73%

Avg conflicts / tx

3.15

Longest chain

16 deep

Execution timeline

did this block parallelize well?

view

block #73,679,354  ·  34 txs across 16 waves  ·  depth 16
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

wave w13

wave w14

wave w15

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

0xc0e19e54…8023

0xd32edf…ff58

23 touches
66 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0x1027390d…a150

0x065c9d…c394

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xb89c7e78…0bf0

0x1b6862…e19c

10 touches
10 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 0xc0e19e54c0…828023

← previous block·next block →recent activity