Block #71,289,423

← previous blocknext block →recent activity

Analyzing

Block #71,289,423

8 transactions · 8 stateful · 2026-04-29 11:39:34 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,289,423  ·  8 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xa87480dd…905b

0x065c9d…c394

4 touches
1 conflict

0x13700c71…896a

0x065c9d…c394

2 touches
0 conflicts

0x8f313589…99bf

0x065c9d…c394

2 touches
0 conflicts

0xa594a1b0…1ca6

0x065c9d…c394

2 touches
0 conflicts

0xa9d62c78…3fa9

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000d

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity