Lesson 6: Contract Address Error?

[SquilliamX]

Hi everyone, I have deployed my Hardhat-Simple-Storage to Sepolia but when I console.log the address the new contract that I am deploying, it prints out 0x5FbDB2315678afecb367f032d93F642f64180aa3. And if you search up that address on the sepolia etherscan, you will see that the contract address returned is a old contract that many people have been transferring to already. Why is this and whats going on? Shouldn't I be deploying a brand new contract that I am made for the first time, thus generating a new address for my contract?

deploy.js:

// imports
const { ethers } = require("hardhat")

// async main
async function main() {
  const SimpleStorageFactory = await ethers.getContractFactory("SimpleStorage")// grabs the contract factory
  console.log("Grabbing Contract...") 
  const simpleStorage = await SimpleStorageFactory.deploy()
  await simpleStorage.waitForDeployment()

  console.log(`Deployed contract: ${simpleStorage.target}`)
}

// async function verify(contract)

//main
main().catch((error) => {
  console.error(error);
  process.exitCode = 1;
});

my terminal:

$ yarn hardhat run scripts/deploy.js 
yarn run v1.22.19
Grabbing Contract...
Deployed contract: 0x5FbDB2315678afecb367f032d93F642f64180aa3
Done in 3.26s.

[SquilliamX]

"The behavior you're witnessing is a quirk of the hardhat local development environment. When you run a script with the default hardhat network, it spins up an instance of the Ethereum Virtual Machine (EVM) locally for development and testing. The address 0x5FbDB2315678afecb367f032d93F642f64180aa3 is the default first address produced by Hardhat's local network. You're not the only one to see this address during local testing...
Ensure you're correctly specifying the --network sepolia flag when you run your deployment script. This flag tells Hardhat to use the Sepolia network configuration." -ChatGPT

After adding --network sepolia, my contract was deployed on Sepolia and produced a new contract address!