Autorefresh is OFF

Tx hash: a6ba7338d5f4a7e43c509823121e38c5cb0be2e6ce0461f74c384b3483aaa113

Tx prefix hash: a6ba7338d5f4a7e43c509823121e38c5cb0be2e6ce0461f74c384b3483aaa113
Tx public key: 052631427b260ab9d25ac2cef478fa5577f1d5e1c0bd59f61024a7d657db12dd
Timestamp: 1517434210 Timestamp [UCT]: 2018-01-31 21:30:10 Age [y:d:h:m:s]: 02:299:02:59:55
Block: 932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 738492 RingCT/type: no
Extra: 01052631427b260ab9d25ac2cef478fa5577f1d5e1c0bd59f61024a7d657db12dd020800000000084f3d56

2 output(s) for total of 10000.00400000 TUBE

stealth address amount amount idx
00: 80c30c127a7cf5d13190664f51339d04565c9eee9f601f0103810d47366c7b8d 0.00400000 198 of 57976
01: eef174725075b84379b24072aaa555fedcedb482e7cbcb90140db32a642f885a 10000.00000000 970 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



{ "version": 1, "unlock_time": 942, "vin": [ { "gen": { "height": 932 } } ], "vout": [ { "amount": 400000, "target": { "key": "80c30c127a7cf5d13190664f51339d04565c9eee9f601f0103810d47366c7b8d" } }, { "amount": 1000000000000, "target": { "key": "eef174725075b84379b24072aaa555fedcedb482e7cbcb90140db32a642f885a" } } ], "extra": [ 1, 5, 38, 49, 66, 123, 38, 10, 185, 210, 90, 194, 206, 244, 120, 250, 85, 119, 241, 213, 225, 192, 189, 89, 246, 16, 36, 167, 214, 87, 219, 18, 221, 2, 8, 0, 0, 0, 0, 8, 79, 61, 86 ], "signatures": [ ] }


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