Kaspa Explained STPYour own wallet
You control the keys and their backup. Losing them can mean losing access. Never share a recovery phrase with a person, website, or explorer.
Use KAS
Follow your payment.
Sending coins creates a payment, change and a fee. Follow those amounts first, then learn what your wallet controls and what an explorer can actually confirm.
Where your payment, change, and fee go.
A transaction consumes earlier outputs and creates new ones. Payment, change, and fees account for the input value.
Where the amount goesConstructed example
Input12.5 KAS
=Payment7 KAS
Change5.499 KAS
Fee0.001 KAS
Ribbon widths compare payment and change. The fee line is enlarged to remain visible.
Amounts are calculated in whole sompi: 100,000,000 sompi = 1 KAS. This is not a signed transaction or a fee recommendation. Payment and change labels are authored for this example.
Who controls the keys?
An exchange account
The provider controls the keys. Your account balance is a claim on that provider, with its own withdrawal rules and risks.
Wallet directory · Wallet integration documentation · See holdings from Kasware or Kastle
Receive. Send. Verify.
Try the three actions that make up a payment.
1 / 3 · Receive
Share the address. Keep the keys.
Your receiving address is public. Your recovery phrase authorizes access to your wallet and must stay private.
Illustrative wallet
Receive KAS
Your public address
Share with senderAddress
Keep privateRecovery phrase
2 / 3 · Send
Review before you sign.
Check the destination, network, amount, and fee in your wallet. Try a small payment when using a new destination.
Illustrative review
2 KAS
To your intended recipient
NetworkCheck it
DestinationCompare it
FeeReview it
3 / 3 · Verify
Follow the transaction ID.
Check the outputs and acceptance state in an explorer. A screenshot from the sender is not independent evidence. The recipient decides when to treat an accepted payment as settled.
Illustrative explorer
Check the record
Transaction ID → network record
OutputsAmount + destination
AcceptanceProvider observation
SettlementYour policy
A guided illustration. No wallet connection, keys, or real funds.
Read a transaction
A public explorer reports its provider’s view. Check amounts and acceptance, and notice which information is missing.
What these fields establish
Inputs refer to earlier outputs. Outputs specify amounts and spending destinations. An accepting-block identifier is different from the list of blocks containing the transaction.
An address does not establish a person’s identity. Output fields alone do not identify which output is a payment and which is change. A block timestamp does not establish when the sender pressed Send.
Fees are calculated only when all referenced input values and output values are available. Missing data is shown as unavailable, never zero.
If something looks wrong
Not found
Check the transaction ID and network. The provider may be delayed, unavailable, or missing the record.
Included but not accepted
A containing block is not an acceptance receipt. Check the accepting history and any wallet or application error.
Accepted, but no exchange credit
An exchange can require additional work and internal processing. Its crediting policy is separate from Kaspa’s block interval.