Block #73,651,578

← previous blocknext block →recent activity

Analyzing

Block #73,651,578

23 transactions · 20 stateful · 2026-05-10 10:01:46 UTC

Parallelism

57/100

Blocked

70%

Avg conflicts / tx

2.3

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,651,578  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x529acb6a…fcc6

0x065c9d…c394

16 touches
28 conflicts

0x046a928e…0012

0x2a68ba…90c5

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x1d7b4b1e…5fcc

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c2

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

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

28 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity