Block #73,669,343

← previous blocknext block →recent activity

Analyzing

Block #73,669,343

30 transactions · 24 stateful · 2026-05-10 12:01:35 UTC

Parallelism

77/100

Blocked

58%

Avg conflicts / tx

0.97

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,669,343  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf2438038…5fa7

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x3e733ae4…4598

0x34b655…2a6f

8 touches
6 conflicts

0xbfae3955…9a9c

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0xb8228d38…3953

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: 0x34b6552d…112a6f

10 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity