Block #73,348,471

← previous blocknext block →recent activity

Analyzing

Block #73,348,471

34 transactions · 23 stateful · 2026-05-09 00:23:04 UTC

Parallelism

82/100

Blocked

39%

Avg conflicts / tx

0.53

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,348,471  ·  34 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb569cc30…6e82

0xd32edf…ff58

9 touches
10 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x44d7acbf…e67f

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

10 conflicts on slot 0xb569cc307b…9a6e82

← previous block·next block →recent activity