Autorefresh is OFF

Tx hash: 1fd83b7e3ff0c94b45cd50a32cea358a48d1526af0cd42a9216fe03e46ee1b7f

Tx prefix hash: 7a09d85448d3bf04599ca285fbd38464e1e576b79627e81ce189cc454ccbd94f
Tx public key: bf9cf64da97989cc0f01c440b17c14dce932354613ee6825335e409014cfd483
Timestamp: 1600185380 Timestamp [UCT]: 2020-09-15 15:56:20 Age [y:d:h:m:s]: 00:004:09:47:43
Block: 688237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1445 kB
Tx version: 2 No of confirmations: 3166 RingCT/type: yes/0
Extra: 01bf9cf64da97989cc0f01c440b17c14dce932354613ee6825335e409014cfd483de403f28d165d70de8535fd13542ab583a3e127589b5c6ebe29a666d753f9f9d12170bc331ec4c100b05bf618ca09de3baba82bc7db3e9e43d787805f46436519dc9

1 output(s) for total of 1.83954001 TUBE

stealth address amount amount idx
00: 201fa2352762e23c1c20883f33e5ebb96bf8a168fb2187c452033f6af1c1cfba 1.83954001 25930048 of 0

Check which outputs belong to given BitTube address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them BitTube in this transaction

Tx private key can be obtained using get_tx_key command in bittube-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



More details
source code | explorer version (api): master-2020-03-09-0f3cc6b (1.1) | bittube version: 3.1.0.0-master-34dd77663