← previous blocknext block →recent activity

Analyzing

Block #73,033,891

37 transactions · 29 stateful · 2026-05-07 13:30:06 UTC

Parallelism

73/100

Blocked

72%

Avg conflicts / tx

1.59

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,033,891  ·  37 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x3adf397a…f210

0xd32edf…ff58

13 touches
21 conflicts

0x0b390c61…dc07

0x065c9d…c394

10 touches
10 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x872e51c8…ae2c

0x1b6862…e19c

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

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

21 conflicts on slot 0x3adf397a61…99f210

← previous block·next block →recent activity