Block #73,652,005

← previous blocknext block →recent activity

Analyzing

Block #73,652,005

15 transactions · 14 stateful · 2026-05-10 10:04:38 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,652,005  ·  15 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

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x8c7f2a82…5d27

0x065c9d…c394

3 touches
1 conflict

0x0dbab0bf…4932

0xd32edf…ff58

3 touches
1 conflict

0xb48c7865…a4f4

0x065c9d…c394

3 touches
1 conflict

0x45064d6b…bce9

0x754704…b603

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: 0x065c9d28…a9c394

6 conflicts on slot 0x7f81fb82c1…ec633e

← previous block·next block →recent activity