Block #71,289,407

← previous blocknext block →recent activity

Analyzing

Block #71,289,407

27 transactions · 23 stateful · 2026-04-29 11:39:27 UTC

Parallelism

74/100

Blocked

61%

Avg conflicts / tx

1.07

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,289,407  ·  27 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

0x074e5b71…22e4

0xd32edf…ff58

9 touches
10 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0xb6d6d740…e91e

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

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

10 conflicts on slot 0x074e5b7143…db22e4

← previous block·next block →recent activity