Block #73,223,893

← previous blocknext block →recent activity

Analyzing

Block #73,223,893

36 transactions · 22 stateful · 2026-05-08 10:34:21 UTC

Parallelism

75/100

Blocked

64%

Avg conflicts / tx

1.36

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,223,893  ·  36 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xec8de30b…7bcf

0xd32edf…ff58

17 touches
36 conflicts

0x0b390c61…dc07

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x928d6b23…5370

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

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

36 conflicts on slot 0xec8de30bde…8b7bcf

← previous block·next block →recent activity