Block #73,648,309

← previous blocknext block →recent activity

Analyzing

Block #73,648,309

27 transactions · 21 stateful · 2026-05-10 09:39:47 UTC

Parallelism

63/100

Blocked

71%

Avg conflicts / tx

2.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,648,309  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x288c330e…6f99

0xd32edf…ff58

19 touches
45 conflicts

0xb159af88…a9e7

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xd53220ed…4737

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

45 conflicts on slot 0x288c330edb…fe6f99

← previous block·next block →recent activity