Block #73,034,038

← previous blocknext block →recent activity

Analyzing

Block #73,034,038

28 transactions · 27 stateful · 2026-05-07 13:31:05 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.96

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,034,038  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xefafbae6…5ea2

0xd32edf…ff58

11 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x32ee90db…decc

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x578e7f66…1b56

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x5dc14a96…6816

0x34b655…2a6f

6 touches
3 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

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

15 conflicts on slot 0xefafbae6ae…c45ea2

← previous block·next block →recent activity