Block #73,270,702

← previous blocknext block →recent activity

Analyzing

Block #73,270,702

10 transactions · 7 stateful · 2026-05-08 15:45:38 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,270,702  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x775ae6c1…5eba

0x065c9d…c394

2 touches
0 conflicts

0x7da12370…0d96

0x065c9d…c394

2 touches
0 conflicts

0x7f6a1311…bbd1

0x065c9d…c394

2 touches
0 conflicts

0xc43e0178…569e

0x065c9d…c394

2 touches
0 conflicts

0xd347abd1…6e0e

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

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity