The money left, and it isn't on the other side: for a crypto transfer that's business as usual, not a disaster.
A transfer first lands in the network's queue and gets confirmed later, sometimes minutes, sometimes longer. Here's what to check before sending so the coins don't go astray, how to look up a transfer's status by its transaction hash (its ID on the network, a long string of letters and digits), and what to do if you paid for a subscription and the plan didn't switch on.
wallet → queue → block → confirmations └─ this is where it "hangs" [!] "unconfirmed" ≠ "lost" it can't fall out of the queue and vanish
Before sending: address and network
Two mistakes lose money more often than anything else, and both are visible before you hit Send.
A typo in the address. A wallet address has a checksum built in, so an address with a typo simply fails validation. In Bitcoin and TRON it's the last bytes of the address, computed from the rest. In Ethereum the sum hides in the letter case: that's why an 0x… address mixes upper and lowercase, that's the ERC-55 standard at work. Paste the address into the wallet address check: it'll tell you which network it belongs to and whether the sum adds up.
The wrong network. This one is worse than a typo, because it passes validation. USDT exists on several networks at once: TRC-20 on TRON, ERC-20 on Ethereum, BEP-20 on BNB Smart Chain, and others. An 0x… address looks identical across the whole Ethereum family, so the wallet happily sends, and the recipient sees nothing: the coins sit on the network you picked when sending, while they're waiting on a different one. Sometimes an exchange's support can dig them out, often not.
One rule: the network you send on has to match the network the recipient specified. Not "similar," the same one. A TRON address starts with T, Ethereum and BNB Smart Chain addresses start with 0x, and 0x alone doesn't tell you the network.
T… TRON (USDT TRC-20)
0x… Ethereum OR BSC OR others
└─ can't tell by the address,
the recipient names the net
1… 3… bc1… BitcoinHow to pay for 404 VPN with crypto
At 404 VPN, crypto payments go through the Trybit payment service: USDT, BTC, ETH and others. The plan switches on by itself a few minutes after the network confirms the transfer; there's nothing to activate by hand.
For USDT, the payment page has a network selector. The recommended one is BNB Smart Chain (BEP-20): on TRON and Ethereum a transfer fee gets added on top of the invoice, and you've got to account for it, or less arrives than was billed. Which network to pick is shown right on the payment page, and that's the only place to take the address from: not from an old email, not from a chat.
If paying from your phone by QR is easier, the crypto payment QR packs the address and amount into one code the wallet reads whole. And to turn satoshis into bitcoin or gwei into ether, so you know what it is in units you're used to, there's the crypto unit converter.
Where is my crypto transfer? Check the hash
Paste the transaction hash into the transfer status check. The network is detected automatically: Bitcoin, Ethereum, TRON, including USDT TRC-20. The page shows whether the transfer arrived, how many confirmations it's collected, and why it might be hanging. The data comes straight from the network explorers, mempool.space, Blockscout and Tronscan, and the request goes from your browser; our servers aren't involved.
What you'll see and what it means:
"Unconfirmed." The transfer is sitting in the network's queue, waiting to be picked up into a block. Pickup goes by profit: pay a fee below the current going rate, and you wait longer. It can't get lost: either it confirms eventually, or after a few days it drops out of the queue and the coins simply stay with you. Either way, don't send it again.
"Confirmed, N confirmations." The transfer is in a block. The recipient usually waits for several confirmations before treating the money as received, so "1 confirmation" plus "plan didn't switch on" isn't a discrepancy yet, it's waiting.
"Not found." The hash was copied incompletely, or on the wrong network. Check that you pasted the whole string and that the network is the one you sent on.
unconfirmed in the queue, wait 1–2 confirmations in a block, wait more enough recipient will see it not found wrong hash or network └─ none of these statuses means "send it again"
Can you speed up a pending transaction?
On Bitcoin, yes, if the wallet supports it. Either replace the transaction with the same one at a higher fee, that's the RBF mechanism, or spend its output with a new high-fee transaction so a miner has a reason to take both at once. On Ethereum you speed things up by resubmitting the same transaction with the same nonce and a higher gas price. All of this happens in the wallet, not on our page: we don't have, and can't have, access to your keys.
Easier not to get there: before sending, look at what fee the wallet suggests as "normal," and don't go below it.
Paid, but the plan didn't switch on
Here's the order, and the first item is the one that matters most.
- Don't send again. A second transfer won't speed up the first, and the money goes out twice.
- Find the hash in the wallet, in the transaction history, and check the status. Unconfirmed means wait. Confirmed just now means wait a few more minutes; the plan switches on after confirmation, not instantly.
- Check the network. If the USDT went out on ERC-20 while the invoice was BEP-20, the recipient can't see it, and that's already a support ticket, with the hash and the network.
- Enough confirmations, right network, more than half an hour passed, plan still off: write to support and attach the hash. The hash shows everything; nothing else is needed.
[ ] did NOT send again
[ ] hash found, status checked
[ ] network matches the invoice
[ ] waited after confirmation
[ ] support, with the hash
└─ the hash settles it faster
than any descriptionHonestly, here's what I'd do: check the address in the tool, match the network against what the payment page says, send, copy the hash and check it five minutes later. That's it. I wouldn't send again under any circumstances until I'd seen the first one's status.
Crypto transfers are public and final
Blockchain transfers are public: anyone with the hash or the address sees the amount and both sides' addresses. That's not a leak, that's how the network works. You can only hide the link between an address and you, not the transfer itself. And a crypto payment doesn't come back at the push of a button: a confirmed transfer can't be canceled by us or by you, so the checks before sending matter more than the checks after.
The key to all of this, the wallet's seed phrase, deserves its own treatment: how to store it and why you never type it into websites is in seed phrase: what it is and how to store it.
If the status makes no sense and support hasn't answered yet, give an AI the hash and the network and it'll explain what's visible.
Help me understand what's going on with my
crypto transfer.
Network: (TRON / Ethereum / BSC / Bitcoin /
don't know).
Coin: (USDT / BTC / ETH / other).
Status on the check: (unconfirmed / N
confirmations / not found).
Time elapsed: (minutes / hours).
Network on the recipient's invoice: (which one).
Tell me if this is normal, whether to wait, and
whether the coins went to the wrong network.
Don't suggest sending again.In short
Before sending: address through the checker, same network the recipient named, and 0x alone doesn't tell you which. After: hash into the status check, "unconfirmed" means wait, don't send again. The plan switches on by itself a few minutes after confirmation. Didn't switch on: hash, network, time, then support with the hash.
