Block #73,374,900

← previous blocknext block →recent activity

Analyzing

Block #73,374,900

18 transactions · 16 stateful · 2026-05-09 03:18:53 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,374,900  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf867412a…2e8e

0xd32edf…ff58

9 touches
10 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x485d2778…aa60

0x1b6862…e19c

6 touches
3 conflicts

0x4ade5778…86a3

0x065c9d…c394

5 touches
3 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

10 conflicts on slot 0xf867412a2e…2d2e8e

← previous block·next block →recent activity