Block #73,670,908

← previous blocknext block →recent activity

Analyzing

Block #73,670,908

12 transactions · 10 stateful · 2026-05-10 12:12:08 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,670,908  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb1cbae67…bda4

0xd32edf…ff58

9 touches
10 conflicts

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x57ec7d97…285c

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x7727b646…f20b

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

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

10 conflicts on slot 0xb1cbae67d9…4cbda4

← previous block·next block →recent activity