Block #73,654,971

← previous blocknext block →recent activity

Analyzing

Block #73,654,971

34 transactions · 26 stateful · 2026-05-10 10:24:41 UTC

Parallelism

68/100

Blocked

54%

Avg conflicts / tx

1.82

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,654,971  ·  34 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xc0545676…f022

0xd32edf…ff58

21 touches
55 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x285245b3…5ffb

0x065c9d…c394

4 touches
1 conflict

0x7727b646…f20b

0x065c9d…c394

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

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 0xc054567653…24f022

← previous block·next block →recent activity