Block #71,558,353

← previous blocknext block →recent activity

Analyzing

Block #71,558,353

10 transactions · 8 stateful · 2026-04-30 17:35:35 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,558,353  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6cb1ffaf…7433

0x065c9d…c394

3 touches
1 conflict

0xa621e9a6…0cf3

0x065c9d…c394

3 touches
1 conflict

0xb0705ffe…3124

0x065c9d…c394

3 touches
1 conflict

0x4021a36b…8e3b

0x065c9d…c394

3 touches
1 conflict

0x185496e9…cb1e

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity