Block #71,696,686

← previous blocknext block →recent activity

Analyzing

Block #71,696,686

26 transactions · 20 stateful · 2026-05-01 08:56:21 UTC

Parallelism

85/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,696,686  ·  26 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

0xefb6b40b…5dce

0xd32edf…ff58

7 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x03149f74…c647

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xd59f6ed1…03e8

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0xefb6b40bab…355dce

← previous block·next block →recent activity