Reading from NEAR testnet…
Reading from NEAR testnet…
4UTCL4XdBDkVHcernfFqXNV6rXmTEaG1X1ykp68uE8wZ
A step failed but the transaction finished. Contracts can catch a failed step and carry on.
davididol.testnet to usdce.ft.ref-labs.testnet
ft_transfer_call() with 1 yoctoNEAR
{
"receiver_id": "exchange.ref-dev.testnet",
"amount": "1080000000",
"msg": "{\"force\": 0, \"actions\": [{\"pool_id\": 758, \"token_in\": \"usdce.ft.ref-labs.testnet\", \"token_out\": \"wrap.testnet\", \"amount_in\": \"1080000000\", \"min_amount_out\": \"1\"}]}"
}EVENT_JSON:{"standard":"nep141","version":"1.0.0","event":"ft_transfer","data":[{"old_owner_id":"davididol.testnet","new_owner_id":"exchange.ref-dev.testnet","amount":"1080000000"}]}usdce.ft.ref-labs.testnet to exchange.ref-dev.testnet · failed
ft_on_transfer()
{
"sender_id": "davididol.testnet",
"amount": "1080000000",
"msg": "{\"force\": 0, \"actions\": [{\"pool_id\": 758, \"token_in\": \"usdce.ft.ref-labs.testnet\", \"token_out\": \"wrap.testnet\", \"amount_in\": \"1080000000\", \"min_amount_out\": \"1\"}]}"
}Smart contract panicked: panicked at 'E102: invalid token id', ref-exchange/src/simple_pool.rs:241:14
usdce.ft.ref-labs.testnet to usdce.ft.ref-labs.testnet
ft_resolve_transfer()
{
"sender_id": "davididol.testnet",
"receiver_id": "exchange.ref-dev.testnet",
"amount": "1080000000"
}EVENT_JSON:{"standard":"nep141","version":"1.0.0","event":"ft_transfer","data":[{"old_owner_id":"exchange.ref-dev.testnet","new_owner_id":"davididol.testnet","amount":"1080000000","memo":"refund"}]}3 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":"4UTCL4XdBDkVHcernfFqXNV6rXmTEaG1X1ykp68uE8wZ","sender_account_id":"davididol.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.