Block #73,653,346

← previous blocknext block →recent activity

Analyzing

Block #73,653,346

15 transactions · 12 stateful · 2026-05-10 10:13:40 UTC

Parallelism

60/100

Blocked

58%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,653,346  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x122efa6c…50ce

0xd32edf…ff58

11 touches
15 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb25dfb62…ab66

0x065c9d…c394

3 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 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

15 conflicts on slot 0x122efa6cf7…3750ce

← previous block·next block →recent activity