Block #73,488,330

← previous blocknext block →recent activity

Analyzing

Block #73,488,330

8 transactions · 7 stateful · 2026-05-09 15:53:41 UTC

Parallelism

38/100

Blocked

57%

Avg conflicts / tx

1.25

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,488,330  ·  8 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0bf9c1ae…844d

0x065c9d…c394

3 touches
1 conflict

0x6e6274e1…ae4d

0x065c9d…c394

3 touches
1 conflict

0x03c18f0f…0083

0x065c9d…c394

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity