← previous blocknext block →recent activity

Analyzing

Block #73,328,464

27 transactions · 19 stateful · 2026-05-08 22:10:04 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

1.67

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,328,464  ·  27 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

0x1d0eea34…7b31

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x46cb45de…a567

0x188d58…ea8e

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x09beabbc…065c

0x188d58…ea8e

6 touches
3 conflicts

0x09beabbc…065d

0x188d58…ea8e

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

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

36 conflicts on slot 0x1d0eea3452…0f7b31

← previous block·next block →recent activity