Block #71,560,710

← previous blocknext block →recent activity

Analyzing

Block #71,560,710

24 transactions · 17 stateful · 2026-04-30 17:51:17 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,560,710  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x2e959758…c63e

0xd32edf…ff58

7 touches
6 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x1e9e9bb8…360f

0x34b655…2a6f

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xbc04d98e…a484

0x34b655…2a6f

4 touches
1 conflict

0xc4eb89d3…ddad

0x34b655…2a6f

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

6 conflicts on slot 0x2e95975880…1dc63e

← previous block·next block →recent activity