Block #71,421,522

← previous blocknext block →recent activity

Analyzing

Block #71,421,522

9 transactions · 7 stateful · 2026-04-30 02:20:13 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,421,522  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0xb138d087…4689

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x1cf9719b…7973

0x065c9d…c394

2 touches
0 conflicts

0x3c60bf58…edfb

0x065c9d…c394

2 touches
0 conflicts

0x74cb14a3…9fd2

0x065c9d…c394

2 touches
0 conflicts

0xd2a73f7a…293d

0x065c9d…c394

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

1 conflict on slot 0x84fb2a3669…b5db89

← previous block·next block →recent activity