Block #73,375,004

← previous blocknext block →recent activity

Analyzing

Block #73,375,004

15 transactions · 14 stateful · 2026-05-09 03:19:34 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,375,004  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x3f7fd82b…6bb4

0x065c9d…c394

6 touches
3 conflicts

0x13f270d7…e1ea

0xd32edf…ff58

5 touches
3 conflicts

0x0488f6a5…92bd

0x065c9d…c394

5 touches
3 conflicts

0xc9168fc0…1533

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity