Block #73,698,306

← previous blocknext block →recent activity

Analyzing

Block #73,698,306

25 transactions · 17 stateful · 2026-05-10 15:17:01 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,698,306  ·  25 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

0x6a3b2771…61ac

0xd32edf…ff58

11 touches
15 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x7cb55150…4d57

0x065c9d…c394

3 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001c

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002c

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

15 conflicts on slot 0x6a3b2771b5…9361ac

← previous block·next block →recent activity