Block #71,555,636

← previous blocknext block →recent activity

Analyzing

Block #71,555,636

16 transactions · 13 stateful · 2026-04-30 17:17:26 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,555,636  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x68b59f59…f585

0xd32edf…ff58

5 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0xab2a87f1…eafd

0x1b6862…e19c

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

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

3 conflicts on slot 0x68b59f5923…d0f585

← previous block·next block →recent activity