← previous blocknext block →recent activity

Analyzing

Block #73,660,432

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

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,660,432  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0xd41b74dd…e4a6

0x065c9d…c394

5 touches
3 conflicts

0xf6eee0f3…a516

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x38524fae…9deb

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd2b65c96…86d1

0x065c9d…c394

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity