Block #71,742,317

← previous blocknext block →recent activity

Analyzing

Block #71,742,317

17 transactions · 13 stateful · 2026-05-01 14:00:11 UTC

Parallelism

71/100

Blocked

46%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,742,317  ·  17 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

0xa4e3b3b1…0911

0x2a68ba…90c5

8 touches
6 conflicts

0x5e55c800…8171

0xa6afd3…d132

7 touches
6 conflicts

0x11b69a7e…334e

0xee8c0e…1242

6 touches
3 conflicts

0x8f3545be…7c43

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

0x794b8f81…3eac

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xa4e3b3b1bb…130911

← previous block·next block →recent activity