Block #71,065,258

← previous blocknext block →recent activity

Analyzing

Block #71,065,258

9 transactions · 8 stateful · 2026-04-28 10:47:15 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,065,258  ·  9 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

0x5ff9e831…6008

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x782c859d…0424

0x065c9d…c394

3 touches
1 conflict

0xed1fd057…95ff

0x065c9d…c394

3 touches
1 conflict

0x43d64cd9…98e1

0x065c9d…c394

3 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5d

0x188d58…ea8e

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

1 conflict on slot 0x5ff9e83175…0f6008

← previous block·next block →recent activity