Block #73,434,050

← previous blocknext block →recent activity

Analyzing

Block #73,434,050

11 transactions · 11 stateful · 2026-05-09 09:52:33 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,434,050  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x1ed0bedf…a289

0xd32edf…ff58

3 touches
1 conflict

0x277e5f1c…e691

0x065c9d…c394

2 touches
0 conflicts

0x0ef74796…cd18

0x0a3323…0a3c

2 touches
0 conflicts

0x366be501…7a02

0x0a3323…0a3c

2 touches
0 conflicts

0xff393f19…4dd2

0x0a3323…0a3c

2 touches
0 conflicts

0x00000000…0000

0x0d73bf…be07

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 0x0000000000…00003d

← previous block·next block →recent activity