Block #73,328,336

← previous blocknext block →recent activity

Analyzing

Block #73,328,336

23 transactions · 19 stateful · 2026-05-08 22:09:14 UTC

Parallelism

65/100

Blocked

58%

Avg conflicts / tx

1.39

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,328,336  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x861d70e4…96be

0xd32edf…ff58

13 touches
21 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

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: 0xd32edf66…9fff58

21 conflicts on slot 0x861d70e406…8196be

← previous block·next block →recent activity