Block #71,289,492

← previous blocknext block →recent activity

Analyzing

Block #71,289,492

14 transactions · 12 stateful · 2026-04-29 11:40:01 UTC

Parallelism

64/100

Blocked

58%

Avg conflicts / tx

0.93

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,289,492  ·  14 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

0x076a71a4…318c

0xd32edf…ff58

9 touches
10 conflicts

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xac808a27…82db

0x34b655…2a6f

4 touches
1 conflict

0xecd87a39…d9c5

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x3254d19b…f714

0x34b655…2a6f

2 touches
0 conflicts

0x3e0f56fb…e78f

0x34b655…2a6f

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

10 conflicts on slot 0x076a71a49d…03318c

← previous block·next block →recent activity