Block #71,065,403

← previous blocknext block →recent activity

Analyzing

Block #71,065,403

9 transactions · 8 stateful · 2026-04-28 10:48:13 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,065,403  ·  9 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x41755291…977f

0x131a2e…0da9

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x222ae6f9…c592

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xac9fc41c…e8bc

0x065c9d…c394

2 touches
0 conflicts

0xe1ef7276…c14b

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity