Block #71,065,629

← previous blocknext block →recent activity

Analyzing

Block #71,065,629

9 transactions · 8 stateful · 2026-04-28 10:49:44 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6db8c1fe…8427

0x065c9d…c394

4 touches
1 conflict

0xc0a6feef…c424

0x065c9d…c394

4 touches
1 conflict

0xd0e8ff37…265a

0x065c9d…c394

4 touches
1 conflict

0xf89a87e0…803b

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xcd621226…2df8

0x368ee5…7ca4

2 touches
0 conflicts

0x5d8373b9…233d

0x44b60b…f711

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity