Block #71,421,669

← previous blocknext block →recent activity

Analyzing

Block #71,421,669

19 transactions · 15 stateful · 2026-04-30 02:21:12 UTC

Parallelism

63/100

Blocked

60%

Avg conflicts / tx

1.26

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,421,669  ·  19 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

0x7f5aa818…7714

0xd32edf…ff58

11 touches
15 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x63ddbef7…dbef

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb8

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 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: 0xd32edf66…9fff58

15 conflicts on slot 0x7f5aa8181a…e57714

← previous block·next block →recent activity