Reading from NEAR testnet…
Reading from NEAR testnet…
AztXkhhnHbHWYFWA7jpJK6dcTEr6S3bxaM8YGVEisyu2
A step failed but the transaction finished. Contracts can catch a failed step and carry on.
zavodil.testnet to dev-1663796869861-87905254082896
withdraw_from_telegram()
{
"telegram_account": 1234,
"account_id": "grant.testnet",
"token_id": "token.zavodil.testnet"
}@grant.testnet is withdrawing 0 of "token.zavodil.testnet" from telegram account 1234
dev-1663796869861-87905254082896 to token.zavodil.testnet · failed
ft_transfer() with 1 yoctoNEAR
{
"receiver_id": "grant.testnet",
"amount": "0",
"memo": "Claiming tips: 0 of \"token.zavodil.testnet\" from @dev-1663796869861-87905254082896"
}Smart contract panicked: panicked at 'The amount should be a positive number', /host/near-contract-standards/src/fungible_token/core_impl.rs:133:9
dev-1663796869861-87905254082896 to dev-1663796869861-87905254082896
after_ft_transfer_balance()
{
"telegram_account": 1234,
"amount": "0",
"token_account_id": "token.zavodil.testnet"
}Token token.zavodil.testnet withdraw by telegram account 1234 failed. Amount to recharge: 0
4 automatic refund steps from the network not shown.
This page reads FastNEAR's public transaction index and stores nothing. This command asks a NEAR archival node for the same transaction and needs no keys.
curl -s https://archival-rpc.testnet.fastnear.com -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tx","params":{"tx_hash":"AztXkhhnHbHWYFWA7jpJK6dcTEr6S3bxaM8YGVEisyu2","sender_account_id":"zavodil.testnet","wait_until":"FINAL"}}'Vouch has its own page because testnet.nearblocks.io stopped indexing on 27 Sep 2026, so it can't show newer transactions.