Autorefresh is ON (10 s)

Tx hash: 0d0756a341cde0a86964f6126efa11d7c9490a1b9f32534ae970da22db188c74

Tx prefix hash: 0d0756a341cde0a86964f6126efa11d7c9490a1b9f32534ae970da22db188c74
Tx public key: f1a1e17f97e523c2b24aca3d80aff64d61b1a613ccacf3ff6930c8b672cd8913
Timestamp: 1517406850 Timestamp [UCT]: 2018-01-31 13:54:10 Age [y:d:h:m:s]: 05:050:12:40:34
Block: 273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1340505 RingCT/type: no
Extra: 01f1a1e17f97e523c2b24aca3d80aff64d61b1a613ccacf3ff6930c8b672cd8913020800000000025cab5d

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: bd240f5b07281ca82289f3248246b270f2fa2471588e48afe811a7776902e2ae 0.00100000 39 of 60494
01: 2930693a75f1b323549670bf140e1cd2cd765317428dadb4a4452217374ee7f6 10000.00000000 287 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 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: