Block #71,557,641

← previous blocknext block →recent activity

Analyzing

Block #71,557,641

23 transactions · 10 stateful · 2026-04-30 17:30:47 UTC

Parallelism

91/100

Blocked

10%

Avg conflicts / tx

0.04

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,557,641  ·  23 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

0x00f245ce…1e10

0x34b655…2a6f

4 touches
1 conflict

0x50c2960c…5f37

0x34b655…2a6f

4 touches
1 conflict

0x53dcbe77…b8e8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x6737ee07…9978

0x34b655…2a6f

4 touches
1 conflict

0x94710b77…a921

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

1 conflict on slot 0x00f245ce7e…641e10

← previous block·next block →recent activity