Block #71,070,410

← previous blocknext block →recent activity

Analyzing

Block #71,070,410

34 transactions · 28 stateful · 2026-04-28 11:21:37 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.82

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,070,410  ·  34 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xcd23707a…3548

0xd32edf…ff58

7 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

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: 0x34b6552d…112a6f

6 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity