Block #73,506,814

← previous blocknext block →recent activity

Analyzing

Block #73,506,814

30 transactions · 19 stateful · 2026-05-09 17:56:52 UTC

Parallelism

63/100

Blocked

63%

Avg conflicts / tx

1.9

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,506,814  ·  30 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

0xacaac2e6…b866

0xd32edf…ff58

21 touches
55 conflicts

0x5860c4f3…0c39

0x3bd359…433a

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x490911cc…5fea

0x0c65a0…0852

4 touches
1 conflict

0x00000000…0002

0xbab229…9388

4 touches
1 conflict

0x00000000…0003

0xbab229…9388

4 touches
1 conflict

0x00000000…0000

0xbab229…9388

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

2 touches
0 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

55 conflicts on slot 0xacaac2e6cf…58b866

← previous block·next block →recent activity