Autorefresh is ON (10 s)

Tx hash: fa73e5c474e774cd0362401825e462d915e9803031558c19b03fa262543159a9

Tx prefix hash: 6ad165cdf109f3bb69abcb9d94950af10e2c701a0086683a41ea33329b14e91a
Tx public key: dbde40519638a7256a43578c78b679476f67724c2784af80d58dd04f0eeab5e7
Timestamp: 1663898683 Timestamp [UCT]: 2022-09-23 02:04:43 Age [y:d:h:m:s]: 00:006:15:47:39
Block: 1211611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1416 kB
Tx version: 2 No of confirmations: 4785 RingCT/type: yes/0
Extra: 01dbde40519638a7256a43578c78b679476f67724c2784af80d58dd04f0eeab5e7de40543a2f94b590d93a61d85ce2007983cee054e10054b8a2ce0b208c35e1ff96c4536ed0104e106787632eabf077f20ffb9fcb1e29453c2ab64c1b205481eaa165

1 output(s) for total of 0.00000001 TUBE

stealth address amount amount idx
00: bc854a2ab889a19cd9781c285c8c3a641417782fbf0f4d5ff42155e119408a80 0.00000001 26479642 of 44438

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