Block #73,660,499

← previous blocknext block →recent activity

Analyzing

Block #73,660,499

22 transactions · 13 stateful · 2026-05-10 11:01:52 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,660,499  ·  22 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

0xe6da49a1…ff7e

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x630c7f67…dd88

0x065c9d…c394

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0004

0x63e48b…53f2

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 0xe6da49a1b7…e7ff7e

← previous block·next block →recent activity