Block #73,651,966

← previous blocknext block →recent activity

Analyzing

Block #73,651,966

27 transactions · 24 stateful · 2026-05-10 10:04:23 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.59

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,651,966  ·  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

0x7f81fb82…633e

0x065c9d…c394

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0x150af51d…9c42

0x34b655…2a6f

6 touches
3 conflicts

0x23114fac…630a

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0x5f450515…3bc4

0x34b655…2a6f

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 0x7f81fb82c1…ec633e

← previous block·next block →recent activity