Block #73,651,524

← previous blocknext block →recent activity

Analyzing

Block #73,651,524

35 transactions · 24 stateful · 2026-05-10 10:01:25 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,651,524  ·  35 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x9a50ae05…b681

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

2 touches
0 conflicts

0x4dae6c80…0d79

0x6657d1…8ccc

2 touches
0 conflicts

0x81955a0a…29ee

0x6657d1…8ccc

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

10 conflicts on slot 0x9a50ae0523…5ab681

← previous block·next block →recent activity