Block #73,651,520

← previous blocknext block →recent activity

Analyzing

Block #73,651,520

50 transactions · 32 stateful · 2026-05-10 10:01:23 UTC

Parallelism

78/100

Blocked

63%

Avg conflicts / tx

1.44

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,651,520  ·  50 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xa9783a5e…f28d

0xd32edf…ff58

21 touches
55 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x03100cc9…9fb9

0x34b655…2a6f

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x7c403af1…31b1

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

55 conflicts on slot 0xa9783a5e60…33f28d

← previous block·next block →recent activity