Block #73,651,530

← previous blocknext block →recent activity

Analyzing

Block #73,651,530

21 transactions · 19 stateful · 2026-05-10 10:01:27 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,651,530  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x72b77ca8…5d1b

0x34b655…2a6f

6 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

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: 0x34b6552d…112a6f

6 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity