Block #71,683,631

← previous blocknext block →recent activity

Analyzing

Block #71,683,631

17 transactions · 11 stateful · 2026-05-01 07:29:22 UTC

Parallelism

76/100

Blocked

36%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,683,631  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x9002fb60…d068

0xd32edf…ff58

7 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x1334b5d6…5a17

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xcd4d0c58…99c5

0x1b6862…e19c

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0002

0xa7283d…0ace

2 touches
0 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

6 conflicts on slot 0x9002fb6056…9ad068

← previous block·next block →recent activity