Tx hash: a0b40507357c3366f86282ef989d2fba065ea31b5c3410ca2f7ff0c17bb8d4c8

Tx prefix hash: a0b40507357c3366f86282ef989d2fba065ea31b5c3410ca2f7ff0c17bb8d4c8
Tx public key: a65a984e9f9cfb3be853587d3b9f45dc20efdc5f820293fa18e0d9e72f834d68
Timestamp: 1517422635 Timestamp [UCT]: 2018-01-31 18:17:15 Age [y:d:h:m:s]: 01:318:06:20:18
Block: 686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0889 kB
Tx version: 1 No of confirmations: 490531 RingCT/type: no
Extra: 01a65a984e9f9cfb3be853587d3b9f45dc20efdc5f820293fa18e0d9e72f834d6802080000000016ab7005

1 output(s) for total of 10000.00000000 TUBE

stealth address amount amount idx
00: a4978ca7fd07279c352095c6f8485c497b68c22a063dde221c9ab36ef8ef9566 10000.00000000 722 of 3008

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 NOT sent to the server, as the calculations are done on the client 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 NOT sent to the server, as the calculations are done on the client side



More details
source code | explorer version (api): master-2019-07-08-dbc4cc2 (1.1) | BitTube version: 2.1.0.1-master-release