Block #71,421,788

← previous blocknext block →recent activity

Analyzing

Block #71,421,788

20 transactions · 18 stateful · 2026-04-30 02:21:59 UTC

Parallelism

70/100

Blocked

61%

Avg conflicts / tx

1.45

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,421,788  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0a4b1dcb…71cf

0xd32edf…ff58

11 touches
15 conflicts

0x15698ac9…2a46

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x78694995…f66e

0x1b6862…e19c

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 0x0a4b1dcbe1…f371cf

← previous block·next block →recent activity