Block #73,651,517

← previous blocknext block →recent activity

Analyzing

Block #73,651,517

47 transactions · 32 stateful · 2026-05-10 10:01:22 UTC

Parallelism

72/100

Blocked

63%

Avg conflicts / tx

1.36

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,651,517  ·  47 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xb159af88…a9e7

0x065c9d…c394

16 touches
28 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xd3910c11…6326

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xed863ec8…90d9

0x1b6862…e19c

10 touches
10 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 0xb159af880b…47a9e7

← previous block·next block →recent activity