Block #71,420,631

← previous blocknext block →recent activity

Analyzing

Block #71,420,631

14 transactions · 13 stateful · 2026-04-30 02:14:13 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,420,631  ·  14 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0xcbd23469…a4df

0x34b655…2a6f

4 touches
1 conflict

0x0dd5cdfa…574f

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0xb138d087…4689

0x34b655…2a6f

4 touches
1 conflict

0xbf71a26d…354c

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity