---
title: Swap Hedera (HBAR): 0.0.x account, memo | Sablebolt
description: Swap HBAR for BTC, USDT or another coin, or get Hedera for what you hold — two addresses, no account. Account IDs like 0.0.1234, the memo field, timing.
url: https://sablebolt.io/coin/hedera
---

# Swap Hedera (HBAR)

HBAR is the coin of the Hedera network, where an address is an account ID like 0.0.1234 and a transaction can carry a short memo. Here you can swap HBAR for another coin, or get HBAR for what you hold — with two addresses and no account.

- **Price:** $0.0754

- **24 h:** -0.60%

- **Market cap:** $3.34B

- **24 h volume:** $83.92M

- **Circulating:** 44.33B HBAR

- **Issued of max:** 88.65% of 50.00B

Market data by CoinGecko

## HBAR on Hedera — the facts that matter for a swap

- **Shown here as:** HBAR

- **Address looks like:** 0.0.xxxxxx + memo

- **Confirmations we wait for:** 15

- **Typical arrival after you send:** ≈ 2–6 min

- **Fee token for later moves:** HBAR

- **Extra field:** memo, if the receiver is an exchange

- **Issued by:** The Hedera network (no issuer)

- **Explorer:** [hashscan.io](https://hashscan.io/)

## HBAR key facts — the numbers that do not change daily

- **Mainnet open access:** 16 September 2019announced by Hedera on hedera.com

- **Consensus:** Hashgraphgossip about gossip and virtual voting; asynchronous Byzantine fault tolerant

- **Ordering:** consensus timestampthe median of the times nodes first received the transaction; no blocks, no miners

- **Smallest unit:** 1 tinybar = 0.00000001 HBAR8 decimal places; 1 HBAR = 100,000,000 tinybar

- **Total supply:** 50,000,000,000 HBARfixed; the SDK's Hbar.MAX constant on docs.hedera.com

- **Address format:** 0.0.x account IDshard 0, realm 0 on mainnet since launch

- **Memo:** up to 100 bytes of UTF-8, publicthe form shows a memo field for HBAR; exchanges use it

- **Fees:** set in US dollars, paid in HBARconverted at the live exchange rate; the fee schedule is a system file

- **Transaction validity:** up to 180 secondsa transaction expires if not reached consensus in time

- **Confirmations the site waits for:** 15about 2–6 minutes

Checked on 14 October 2026 against docs.hedera.com (account properties: shardNum.realmNum.accountNum, every mainnet account is 0.0.<num>; transaction properties: memo of up to 100 bytes of UTF-8 visible to all, validity up to 180 seconds, consensus timestamp as the median of node receipt times; hbars: 1 hbar equals 100 million tinybar, the SDK constant Hbar.MAX of 50,000,000,000; hashgraph consensus: gossip, virtual voting, asynchronous Byzantine fault tolerance; mainnet fees: charged in HBAR converted from USD at the live rate; auto account creation), the open-access announcement on hedera.com and the Hiero announcement on lfdecentralizedtrust.org.

## Which network should the HBAR arrive on?

- **Someone else is receiving.:** Ask for their Hedera account ID. It has the form 0.0.x — on the main network the first two numbers are always 0 and the third is the account number. A personal wallet needs no memo.

- **An exchange is receiving.:** Exchanges usually give every customer the same account ID and tell deposits apart by the memo. Copy both the account ID and the memo from the deposit page, and put the memo in the form's memo field. Without it the exchange may not credit the deposit.

- **Your own wallet is receiving.:** Use the account ID the wallet shows. Some wallets also show an EVM-style address starting with 0x for the same account; the form expects the 0.0.x form. HBAR pays its own network fee, so nothing else is needed to move it again.

- **Nothing decides it.:** There is one network for HBAR, so the only choices are the amount and whether a memo is needed. When in doubt about the memo: a personal wallet does not need one, an exchange almost always does.

## How to swap HBAR

1. Choose the two sides. Open the form on the home page, pick HBAR as what you send, then what you want to receive — or the other way round when HBAR is what you want to end up with. There is no separate route page for HBAR yet.
2. Enter the amount. The estimate updates as you type and refreshes every 60 seconds. The minimum for the pair is shown under the field.
3. Paste the receiving address, and the memo if there is one. For an HBAR payout the form checks for an account ID of the form 0.0.x and shows a memo field. Fill the memo only if the receiving service shows one.
4. Send the deposit and follow it. You get a one-time deposit address. Send the exact amount, in one transaction. The status page shows each stage and both transaction hashes; the Hedera side can be looked up on HashScan.

## Before you send — checklist

- The receiving address is a Hedera account ID (0.0.x), not a 0x address and not an account ID from another network.
- If the receiver is an exchange, the memo from its deposit page is in the form's memo field, exactly as shown.
- If a personal wallet is receiving, the memo field is empty.
- The amount is sent in one transaction, from a wallet you control.
- The status link is saved.

## What a HBAR swap costs

- **The rate is floating.** The estimate follows the market and is fixed when your deposit confirms. Our route data counts 15 confirmations for an HBAR deposit; on Hedera that passes in a few minutes.
- **The network fee for the payout** is shown in the form and already taken out of "You get". An HBAR payout is a plain transfer and is among the cheaper ones here.
- **Sending the deposit** costs your wallet a Hedera fee in HBAR. That fee is not part of the swap.

Small amounts cost more in percent, because the payout network fee is the same size for a small swap as for a large one.

## How Hedera works for a sender — hashgraph, timestamps, fees in dollars

The numbers below were checked on 14 October 2026 against docs.hedera.com.

### No blocks: a consensus timestamp

Hedera orders transactions with the hashgraph algorithm. Each node gossips about the transactions it knows to its peers, and the gossip carries the record of who told whom and when — the documentation's phrase is gossip about gossip. From that record every node can work out how every other node would vote on the order of events without any votes being sent, which is called virtual voting. The algorithm is asynchronous Byzantine fault tolerant: no single member or small group can stop the community from reaching consensus. The output for each transaction is a consensus timestamp, derived from the median of the times the nodes first received it, and the documentation says that within seconds everyone knows with certainty where the transaction sits in history.

There is no leader or miner, and nothing that goes stale in the way a block can. For a sender the result is that a transfer either reaches consensus within seconds or expires: every transaction has a validity window of up to 180 seconds from its start time, and one that has not reached consensus by then is simply never applied.

### What the site waits for

The route data this site is built from waits for **15** confirmations on an HBAR deposit. Hedera does not have blocks to count, so read this as the provider's waiting rule — a short fixed delay after the consensus timestamp — rather than a count of anything on the chain. In practice a swap from HBAR starts in about 2–6 minutes, and the deposit itself was final within seconds.

| Stage | For the deposit |
|---|---|
| Submitted | The transaction is gossiped; a receipt confirms consensus within seconds |
| Consensus timestamp | Final; visible on HashScan with its transfers and memo |
| Provider's 15-confirmation delay | The status page counts; the rate is fixed at the end of it |

### Fees set in dollars

Hedera's fees are quoted in US dollars and paid in HBAR, converted at the live exchange rate at the moment of the transaction; the mainnet fee page says prices come from a fee schedule stored in a system file and may change, and describes a base fee for a standard transfer with extras for additional signatures and the like. The number a sender needs to know is in the wallet at the moment of sending, and it is small. The form shows the payout fee in HBAR and takes it out of "You get"; no price is written here.

### Accounts, and receiving without one

A Hedera account is identified by an account ID — three numbers, shard.realm.account — and on mainnet the first two have been 0 since launch, so every address is 0.0.<number>. An account must exist before it can hold a balance, which raises the question of a first payout. The documentation's auto account creation covers it: a transfer to an alias — a public key or an EVM address — creates the account on the way, with the payer of the transfer covering the creation fee. The form, however, expects the 0.0.x form of the receiving account, so the normal case is a wallet that already has one.

**Final in seconds, counted in minutes.** The deposit is settled long before the status page moves. The time on the status page is the provider's rule; the thing to get right is the memo, which the next section is about.

## Hedera addresses and memos — 0.0.x, and when to fill the memo

A Hedera address is an account ID, not a hash of a key. The documentation gives the format as shardNum.realmNum.accountNum and states that every mainnet account ID is 0.0.<num>, both leading segments having been 0 since launch. Checked at docs.hedera.com on 14 October 2026.

| Form | Example shape | What it is | For an HBAR payout here |
|---|---|---|---|
| Account ID | 0.0.1234567 | The account's number on the ledger | accepted |
| Account alias, EVM address | 0.0.<40 hex characters>, or 0x… in wallets | An alias from an ECDSA key; the long-zero form encodes the account number | not accepted — look up the 0.0.x ID |
| Account alias, public key | 0.0.<public key> | An alias from an Ed25519 or ECDSA key before the account is created | not accepted |
| Node account | 0.0.3 and similar | The account of a consensus node | never a destination |

The account ID has no checksum of its own in its plain form, so a wrong digit names a different account — one that may well exist. Paste it, and compare the number with the source. Some tools show an ID with a checksum suffix after a hyphen; the form wants the plain 0.0.x form.

### The memo

Every Hedera transaction can carry a memo: up to 100 bytes of UTF-8, optional, and visible to all participants in the network. Exchanges and other services that keep many customers behind one account use it the way the XRP Ledger uses a destination tag and Stellar uses its memo — one account ID for everyone, and the memo says whose deposit this is. That is why the form shows a memo field for HBAR.

| Receiver | Account ID | Memo |
|---|---|---|
| Your own wallet | the 0.0.x ID the wallet shows | leave empty |
| An exchange | the ID from its HBAR deposit page | copy the memo from the same page, exactly |
| Another person's wallet | their 0.0.x ID | leave empty unless they say otherwise |

A transfer to an exchange without the memo reaches the exchange's account but not your balance there; crediting it afterwards is a request to the exchange's support with the transaction ID. The memo is public on HashScan, so put nothing private in it. (An account also has its own memo, limited to 100 characters — a label on the account, unrelated to the transaction memo and never needed here.)

### What the form accepts

For an HBAR payout, an account ID in the 0.0.x form plus an optional memo. If your wallet shows only a 0x… address for your account, the account ID exists and the wallet can show it; HashScan also resolves a 0x address to its 0.0.x ID.

### Which address to give

1. **Your own wallet:** its account ID, memo empty.
2. **An exchange:** both values from its deposit page; the form has a field for each.
3. **Another person:** their account ID; ask whether a memo is expected (for a personal wallet, it is not).

[Memo, destination tag, payment ID](https://sablebolt.io/blog/memo-destination-tag-payment-id) covers the same field across the coins that have one.

## Checking a Hedera transaction — HashScan, the transaction ID, the memo

A Hedera transaction is identified by a transaction ID of the form accountID@validStartTime — the paying account and the start time in seconds and nanoseconds, such as 0.0.9401@1598924675.82525000 — rather than by a hash alone. The status page links the HBAR side of a swap to HashScan, which was read on 14 October 2026.

**HashScan** opens a transaction with its type (a crypto transfer, for a deposit or payout), its result (success or a failure code), the consensus timestamp, the transaction ID, the fee charged, the memo in plain text, and the transfers: each account debited or credited and by how much, with the node and the fee collection shown as their own lines. An account page lists the balance, every transaction touching the account, and — for an account with an EVM alias — the 0x form next to the 0.0.x ID.

### A deposit you sent

1. Copy the transaction ID from your wallet's history; a hash from the wallet works on HashScan too.
2. Open it on HashScan. Not found after a minute means the transaction never reached consensus — it expired after its validity window, or the wallet never submitted it.
3. Check the transfers: the deposit account from the form credited with the exact amount, and the memo from the form, if there was one, shown in the memo line.
4. The status page then counts the provider's 15 confirmations and moves on its own.

A result other than success means no transfer happened, though a small fee may have been charged. The common codes are an insufficient balance for the amount plus the fee, and an invalid account ID.

### A payout you received

1. Open the transaction from the status page on HashScan.
2. Find your account among the credited transfers. The amount is "You get" from the form; the payout network fee was already taken out.
3. Read the memo line if you gave a memo: it should match what the receiving service expects, character for character.
4. Keep the transaction ID. It is the one thing support on either side will ask for.

### If an exchange says the deposit is missing

Open the payout on HashScan. If the credited account is the exchange's and the memo line shows the memo from its deposit page, the HBAR is there and crediting is the exchange's task — give its support the transaction ID. If the memo line is empty or different, the memo was wrong or missing; the HBAR is still at the exchange's account, and only its support can match it to you. If the credited account is not the exchange's, the account ID in the form was wrong.

[What a block explorer shows about a swap](https://sablebolt.io/blog/what-a-block-explorer-shows-about-a-swap) does the same for other networks; [Reading a swap status page](https://sablebolt.io/blog/reading-a-swap-status-page) explains each stage.

## The mistakes that cost money with HBAR

Hedera's transfers are final in seconds and the network itself rarely surprises anyone. The mistakes are the memo and the account ID.

| Mistake | What happens | What to do |
|---|---|---|
| Payout to an exchange without its memo | The HBAR reaches the exchange's account, not your balance | Contact the exchange's support with the transaction ID; only it can credit the deposit |
| Memo with a typo, or the memo of another service | Same as above | Same as above |
| Memo filled for a personal wallet | Harmless; the memo is public and ignored by the wallet | Nothing — but put nothing private in it |
| Account ID with a wrong digit | The HBAR goes to another account, which may exist | Paste; compare the number. If sent, only the owner of that account can return it |
| Giving a 0x… alias instead of the 0.0.x ID | The form refuses it | Find the account ID in the wallet or on HashScan |
| Sending the deposit without the memo the form showed | The deposit cannot be matched to your swap | Contact [support](https://sablebolt.io/support) with the transaction ID |
| Exchange withdrawal fee taken out of the amount | Less arrives than the form expects | Set the withdrawal so that the amount arriving matches the figure in the form |

### The missing memo

This is the Hedera mistake, and it is the same mistake as on the XRP Ledger, Stellar and TON. The exchange has one account for every customer and reads the memo to know whose deposit arrived. A transfer without it is not lost — it is on the exchange's account, visible on HashScan with your amount and an empty memo line — but it is not yours until a person at the exchange matches it. Every exchange has a procedure for this; it takes time and the transaction ID. Avoid it: copy the memo from the deposit page into the form's memo field, and compare it on the confirmation screen before you send.

The deposit side mirrors it. If the form shows a memo next to the HBAR deposit account, that memo is how your deposit is matched to your swap; a wallet or exchange withdrawal must carry it. Most exchanges' HBAR withdrawal forms have a memo field; if one does not, do not send from there.

### The wrong number

An account ID is a counter, not a hash, and it has no checksum in the plain 0.0.x form. 0.0.1234567 and 0.0.1234576 are both likely to be real accounts. HashScan shows who an account is — its balance, its history, its alias — so a quick look before sending to a new account ID is worth the ten seconds.

### Less arrives than the form expects

Most exchanges deduct their withdrawal fee from the amount you type; the swap runs on what arrived, and under the route's minimum it cannot be processed as a swap at all. The withdrawal screen shows the amount that will actually be sent. [Minimums, maximums and fees on small swaps](https://sablebolt.io/blog/minimums-maximums-network-fees-small-swaps) explains how to read the minimum.

**Nothing here is reversible.** A transaction with a consensus timestamp is final. The memo and the account number are checked by you, not by the network; the form checks only the shape.

## What changed on Hedera, and when — dated, with sources

Hedera has changed its governance and its code base more than its ledger. Three changes matter to someone sending or receiving HBAR; sources are hedera.com, lfdecentralizedtrust.org and docs.hedera.com, read on 14 October 2026.

| Change | When | For a sender | Source |
|---|---|---|---|
| Mainnet open access | 16 September 2019 | Anyone could create an account and transact; the 15-year coin distribution to early purchasers began | hedera.com announcement of 29 August 2019 |
| Auto account creation | 2022 onward | A transfer to a public-key or EVM-address alias creates the account; the payer covers the creation fee | docs.hedera.com, auto account creation |
| Hiero | 16 September 2024 | The network's code base moved to Linux Foundation Decentralized Trust as an open-source project | lfdecentralizedtrust.org; hedera.com |

**Open access, September 2019.** Hedera's announcement of 29 August 2019 set open access to the mainnet beta for Monday, 16 September 2019: from that day any developer could create an account and build on the network, and the first three services were a cryptocurrency, smart contracts and a file service. Mirror node code was open-sourced at the same time, and the announcement marked the start of a 15-year distribution of HBAR to participants in the earlier token agreements. The account ID format, 0.0.x, and the tinybar are unchanged since.

**Auto account creation.** Originally an account had to be created explicitly before it could receive anything. The documentation now describes auto account creation: a transfer to an alias triggers a child account-creation transaction just before the transfer, a new account number is assigned, and the alias is stored on the account. With an EVM-address alias the new account is hollow — it can receive but cannot send or change its properties until it is completed by paying for a transaction signed with the matching key. The form expects an existing 0.0.x account, so this path is background for a swap; it is why a wallet can show a 0x address for a Hedera account at all.

**Hiero, September 2024.** On 16 September 2024, five years to the day after open access, Hedera and Linux Foundation Decentralized Trust announced that the entirety of Hedera's source code — the hashgraph consensus algorithm, the core services, the tooling — was contributed to the foundation as the Hiero project. Hedera's own blog presents Hiero as the open-source foundation the network builds on. Nothing about an account, a memo or a transfer changed; the change is who maintains the software and how.

**Fees.** The fee model has been constant in principle — set in US dollars, paid in HBAR at the live rate — and the schedule is a system file that may change. The documentation's current description adds a base-fee-plus-extras structure for transactions with more signatures or keys than the standard case.

**What has not changed.** 0.0.x account IDs, the 100-byte memo, 8 decimals, 50 billion HBAR, finality in seconds. An account created in 2019 receives HBAR today exactly as it did then.

## Hedera next to Stellar, for a transfer

Hedera and Stellar are the two memo chains on this site that are not the XRP Ledger: fast, cheap, no mining, an account model, and an optional memo that exchanges rely on. For a transfer they feel alike, and they differ in the address, in what a new account needs, and in the memo's shape. Sources: docs.hedera.com, developers.stellar.org and [the Stellar page](https://sablebolt.io/coin/stellar) on this site, 14 October 2026.

|  | Hedera (HBAR) | Stellar (XLM) |
|---|---|---|
| Consensus | hashgraph; consensus timestamp | Stellar Consensus Protocol; ledgers close in seconds |
| Address | account ID 0.0.x | public key G…, 56 characters |
| Memo | up to 100 bytes of UTF-8 text | one of four types; the form's field is MEMO_ID, a number |
| Memo in the form | yes | yes |
| Smallest unit | tinybar, 10⁻⁸ HBAR | stroop, 10⁻⁷ XLM |
| New account | must exist, or be created through an alias | created by the first payment, which must be at least 1 XLM |
| Minimum balance | none for an ordinary account | two base reserves, 1 XLM, locked |
| Fee | set in US dollars, paid in HBAR | 100 stroops per operation and up, in XLM |
| Supply | 50 billion, fixed | about 50 billion; inflation ended October 2019 |
| Confirmations the site waits for | 15, about 2–6 min | 10 ledgers, about 2–6 min |
| Route page | none yet — the form on the [home page](https://sablebolt.io/) | [BTC → XLM](https://sablebolt.io/swap/btc/xlm) |

**The memo.** Both chains carry it, both forms show a field for it, and on both the rule is the same: fill it for an exchange, leave it empty for a wallet. The shape differs. A Hedera memo is free text, up to 100 bytes; an exchange may give you digits, a word or a code, and the form takes it as is. Stellar has four memo types, and the form's field is the ID type — a number — so an exchange that shows only a text memo needs a numeric alternative from its deposit page. A missing memo has the same consequence on both: the funds reach the service, not your balance.

**New accounts and minimum balances.** This is the real difference. A Stellar account exists only once it holds two base reserves — currently 1 XLM — so a first payout to a fresh G… address must be at least that, and the 1 XLM stays locked. Hedera has no minimum balance for an ordinary account, but the account must exist: a payout here goes to an existing 0.0.x ID, and creating one is the receiver's step, not the form's.

**Addresses.** A Stellar public key has a checksum and a fixed length, and a typo is caught. A Hedera account ID is a plain number: a typo names a neighbour. Stellar's trap is the muxed M… address and the C… contract address; Hedera's is the 0x alias in place of the account ID.

**Routes.** XLM has one route page, from BTC, and the fastest payout on this site after it lands. HBAR has none yet: pick it as either side in the form on the home page.

## About HBAR — only what a swapper needs

Hedera is a public network that does not use a chain of blocks in the Bitcoin sense; transactions are ordered by the hashgraph consensus algorithm and get a consensus timestamp once the network agrees on them. HBAR is its native coin and pays every transaction fee. There is no issuer and no contract.

Accounts are the first thing to get used to. A Hedera address is an account ID written as three numbers, shard.realm.account — 0.0.1234, for example. The Hedera documentation describes the format as <shardNum>.<realmNum>.<account>, and on the main network the shard and realm are both 0, so every address starts with 0.0. (checked on 12 October 2026). An account also has an EVM-style alias starting with 0x, used by wallets that talk to Hedera's smart-contract side; the form expects the 0.0.x form.

The second thing is the memo. Every Hedera transaction can carry an optional memo, limited to 100 bytes of UTF-8 text and visible to everyone on the network, per the Hedera documentation on transaction properties. Exchanges use it the way XRP uses a destination tag: one account ID for all customers, and the memo says whose deposit it is. That is why the form shows a memo field for HBAR. Fill it when the receiving service shows one; leave it empty for a personal wallet.

Our route data counts an HBAR deposit as confirmed after 15 confirmations. Hedera does not have blocks in the classic sense, so read this as the provider's waiting rule rather than a count of blocks; in practice a swap from HBAR takes about 2–6 minutes. A swap into HBAR depends on the network you send from.

The explorer for Hedera is HashScan. It shows accounts by their 0.0.x ID, transactions by their ID, and the memo of each transaction in plain text — which is one more reason to put nothing private in a memo.

## FAQ

Do I need a memo?

Only when the receiving address belongs to an exchange or another service that shows one. A personal wallet does not need it. If a deposit page shows a memo, it is required there, and a transfer without it can go uncredited.

What does a Hedera address look like?

An account ID of the form 0.0.x, for example 0.0.1234. On the main network the first two numbers are always 0.

My wallet shows a 0x address for my Hedera account. Can I use it?

The form expects the 0.0.x account ID. Look it up in the wallet, or paste the 0x address into HashScan, which shows the account ID it belongs to.

How long does it take?

A swap from HBAR takes about 2–6 minutes: 15 confirmations in our route data, which pass quickly on Hedera. A swap into HBAR depends on the network you send from — 2–5 minutes from TRON, 4–10 from Ethereum, 21–44 from Bitcoin.

What is the minimum?

It is shown under the amount field for the pair you selected and moves with network fees.

Where is the route page for HBAR?

There is none yet. HBAR is swapped in the form on the home page; pick it as either side and the form shows the rate and the minimum.

What is a tinybar?

The smallest unit of HBAR: 1 HBAR = 100,000,000 tinybar, so amounts have 8 decimal places. The network and the SDKs count in tinybar; wallets and HashScan show HBAR.

I sent HBAR to an exchange without the memo. Is it lost?

No. It is on the exchange's account, visible on HashScan with an empty memo line. Only the exchange can match it to your balance; contact its support with the transaction ID. Here the form has a memo field so that this does not happen.

Can a payout go to an account that does not exist yet?

Not through the form, which expects an existing 0.0.x account ID. Hedera can create an account from a transfer to a key or EVM-address alias, but that is the wallet's path; create the account in your wallet first and give its ID.

How are Hedera fees set?

In US dollars, converted to HBAR at the live rate when the transaction is processed. The form shows the payout fee in HBAR and takes it out of "You get"; your wallet shows the fee for the deposit before you send.

Is the memo private?

No. The documentation says a transaction memo is visible to all participants in the network, and HashScan shows it in plain text. Put only what the receiving service asked for in it.

Is there a refund address?

No. The form asks for the address you send from and the address that receives. If a swap cannot be completed, write to support with the swap ID: every such case is handled by hand.

## Related

### Coins

- [XRP](https://sablebolt.io/coin/xrp)
- [Stellar](https://sablebolt.io/coin/stellar)
- [Gram](https://sablebolt.io/coin/gram)
- [Tether](https://sablebolt.io/coin/tether)
- [Bitcoin](https://sablebolt.io/coin/bitcoin)
- [Solana](https://sablebolt.io/coin/solana)

### Posts

- [Memo, destination tag, payment ID: the coins that need an extra field](https://sablebolt.io/blog/memo-destination-tag-payment-id)
- [Reading a swap status page: every state from waiting to finished](https://sablebolt.io/blog/reading-a-swap-status-page)

## External resources

- [Hedera docs — account properties](https://docs.hedera.com/hedera/core-concepts/accounts/account-properties)
- [Hedera docs — transaction properties (memo)](https://docs.hedera.com/learn/core-concepts/transactions/properties)
- [CoinGecko — Hedera](https://www.coingecko.com/en/coins/hedera-hashgraph)
- [HashScan](https://hashscan.io/)