01The order number corresponds to the exchange, and the hash corresponds to the on-chain transaction

After creating an exchange, the system returns an order number; at this point no payment has been made, and there may be no transaction hash at all. The corresponding on-chain record appears only when you send the asset, the order sends the target asset, or an actual refund occurs.

Therefore, do not paste the order number into a block explorer as a hash query, and do not treat the deposit hash as the sole identifier for the entire exchange. Order queries distinguish the order number from the processing stage.

资料依据：FeilongEX: Explanation of current quote and order fields ↗FeilongEX: Order number and data boundaries ↗

02Use a teaching record example to connect the numbers

The examples only illustrate query relationships: the order number "ORDER-example" corresponds to the entire BTC → USDT exchange; the deposit hash "TX-IN-example" corresponds to the BTC you sent on the Bitcoin network; the outgoing hash "TX-OUT-example" corresponds to the USDT sent out by the FeilongEX order on the TRON network. Only if a refund actually occurs will a refund hash "TX-REFUND-example" appear again.

When troubleshooting, first use the order number to confirm the current stage, then query the corresponding hash on each network. A successful deposit hash only proves that the deposit entered the blockchain record; it cannot replace proof of an outgoing transfer on the target network. The example numbers cannot be used for FeilongEX queries, nor are they payment information.

资料依据：FeilongEX: Explanation of current quote and order fields ↗FeilongEX: Order number and data boundaries ↗Bitcoin Developer Guide: Transaction identifiers and transaction outputs ↗

03First determine which step you want to confirm

To find out whether an order is still processing, use the order number to open Order query; to confirm whether the payment in the wallet is on-chain, use the deposit hash to check the sending network. After receiving the outgoing hash, check the receiving record on the target network.

For example, ETH to SOL involves two networks, and the deposit transaction on Ethereum and the outgoing transaction on Solana should be checked separately. In USDT TRC20 to BTC, you also cannot infer completion of the Bitcoin receipt from a successful TRON deposit.

资料依据：FeilongEX: Explanation of current quote and order fields ↗Ethereum: Transaction status, token transfers, and public data in block explorers ↗

04The estimated quantity is not proof of payment

When an order is created, the estimated sending and estimated receiving amounts are recorded; these numbers describe the order requirements and do not prove that funds have moved. Even if the page already shows a receiving amount, the outgoing transfer may not yet have actually occurred; this needs to be checked together with the outgoing hash and the corresponding on-chain status.

Whether a deposit is recognized must be judged based on records such as the actual amount received and the deposit time. These fields have different meanings in the order interface. If you are unclear why the estimate changed, you can first read the Floating and fixed rate guide.

资料依据：FeilongEX: Explanation of current quote and order fields ↗

05After you have the hash, still check the status and transfer contents

A hash is a search clue, not a guarantee of success. A block explorer may show pending, failed, or successful; when verifying, also check the network, receiving address, asset, and amount. Taking Ethereum as an example, a token transfer should be checked in the token transfer records, not only by the ETH value at the top of the transaction.

If you cannot find the record, first confirm whether the network is correct, whether the hash was copied completely, and whether the sender has broadcast it. If you need to further locate a receipt issue, follow the Not received troubleshooting guide step by step.

资料依据：Ethereum: Transaction status, token transfers, and public data in block explorers ↗

06Save the order number, and distinguish scope when sharing information

FeilongEX currently allows order details to be checked by order number. Based on this lookup method, treat the order number and the complete numbered lookup link as sensitive information; do not post them publicly on forums, comments, or social accounts. When you need assistance, provide them through verified official support channels.

A hash on a public chain can usually be checked by anyone and may also be linked to addresses, amounts, and times. When submitting a support request, state which one is the order number and which one is the deposit or outgoing hash, to avoid mixing different transactions together.

资料依据：FeilongEX: Explanation of current quote and order fields ↗Ethereum: Transaction status, token transfers, and public data in block explorers ↗

FAQ

Is it normal to have an order number but no transaction hash?

It may be normal. Creating an order does not automatically make a payment; whether there is already an on-chain transaction must be checked on the sender side and at the current order stage.

If the deposit hash shows success, does that mean the exchange is complete?

It does not mean that. It can only help verify the deposit transaction; the outgoing transfer of the target asset still needs separate verification.

Can I publicly give the order number to others to help check it?

Not recommended. Anyone who knows the number may be able to see order details; when seeking help, use official support channels.