Block #71,421,904

← previous blocknext block →recent activity

Analyzing

Block #71,421,904

18 transactions · 17 stateful · 2026-04-30 02:22:46 UTC

Parallelism

61/100

Blocked

41%

Avg conflicts / tx

0.89

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,421,904  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

5 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

5 touches
3 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

5 touches
3 conflicts

0xd32f8498…be67

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity