Block #73,639,005

← previous blocknext block →recent activity

Analyzing

Block #73,639,005

33 transactions · 28 stateful · 2026-05-10 08:37:10 UTC

Parallelism

79/100

Blocked

61%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,639,005  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0x9964da26…4db2

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x7425a853…a582

0x34b655…2a6f

6 touches
3 conflicts

0xde1a0ee7…c75b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity