Tx hash: 2b6cdc575ca7cb17acf2d61e162b2ef13da3cc6c926c8805109062227f334e32

Tx prefix hash: 2b6cdc575ca7cb17acf2d61e162b2ef13da3cc6c926c8805109062227f334e32
Tx public key: 7af548e28a32b30c0a28d2e55a7b99fb6fae5117644e23f55da5bf3c11430f9c
Timestamp: 1517422808 Timestamp [UCT]: 2018-01-31 18:20:08 Age [y:d:h:m:s]: 01:315:10:45:01
Block: 691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 488504 RingCT/type: no
Extra: 017af548e28a32b30c0a28d2e55a7b99fb6fae5117644e23f55da5bf3c11430f9c02080000000002149f66

2 output(s) for total of 10000.00300000 TUBE

stealth address amount amount idx
00: d7d03661fcbb6b1f0ff4bbf1b2199e9da4f57d8fbd88a75146d2b067d109bae4 0.00300000 71 of 57727
01: c2b94e278a36b78ba58b961dc3f53417705badab3f5403ef12cc76f7d0cb8897 10000.00000000 727 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