Block #71,446,193

← previous blocknext block →recent activity

Analyzing

Block #71,446,193

21 transactions · 14 stateful · 2026-04-30 05:04:37 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,446,193  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x490f904d…50a8

0xd32edf…ff58

7 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0xb1d63136…d160

0x065c9d…c394

3 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

2 touches
0 conflicts

0x7c403af1…31b1

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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

6 conflicts on slot 0x490f904d2b…7350a8

← previous block·next block →recent activity