Block #71,701,672

← previous blocknext block →recent activity

Analyzing

Block #71,701,672

11 transactions · 11 stateful · 2026-05-01 09:29:28 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,672  ·  11 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

0xf6ba9b21…5532

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe4f849df…152f

0x065c9d…c394

3 touches
1 conflict

0x03d3105e…ba5a

0x065c9d…c394

2 touches
0 conflicts

0x06de1c48…920b

0x065c9d…c394

2 touches
0 conflicts

0x342c36dd…9c9e

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

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 0xf6ba9b21b0…bc5532

← previous block·next block →recent activity