Block #73,374,904

← previous blocknext block →recent activity

Analyzing

Block #73,374,904

21 transactions · 18 stateful · 2026-05-09 03:18:54 UTC

Parallelism

71/100

Blocked

28%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,374,904  ·  21 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

0x056a4fe5…c7d9

0xd32edf…ff58

7 touches
6 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x9ac040c1…8225

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xf7cfe8a6…890d

0x065c9d…c394

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

6 conflicts on slot 0x056a4fe5b4…00c7d9

← previous block·next block →recent activity