Block #73,353,185

← previous blocknext block →recent activity

Analyzing

Block #73,353,185

24 transactions · 18 stateful · 2026-05-09 00:54:31 UTC

Parallelism

63/100

Blocked

67%

Avg conflicts / tx

1.83

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,353,185  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x22e295f5…1bef

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x7c56d7bc…4689

0xd32edf…ff58

7 touches
6 conflicts

0x5cb1ae64…9bd3

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c4

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

21 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity