Autorefresh is OFF

Tx hash: 6aeb3332bf196b5bd8882380668886973619a9bb57830262fc5ea9315192e433

Tx prefix hash: 6aeb3332bf196b5bd8882380668886973619a9bb57830262fc5ea9315192e433
Tx public key: 5aa0c83da21e47bfbf22ab9c6b0062bba906c30d7dc1a28eaf0cdf7b86c7b6cf
Timestamp: 1517424494 Timestamp [UCT]: 2018-01-31 18:48:14 Age [y:d:h:m:s]: 05:057:02:52:45
Block: 727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1344920 RingCT/type: no
Extra: 015aa0c83da21e47bfbf22ab9c6b0062bba906c30d7dc1a28eaf0cdf7b86c7b6cf0208000000006b6035b3

2 output(s) for total of 10000.02000000 TUBE

stealth address amount amount idx
00: f713083b37a3202f45ec124cf23e6ea239f1e2c5f321d64dfbf20f73c54a6565 0.02000000 95 of 151559
01: 374232137adfcc49e70d46ffed572f7cf7c491c950f049230e45da4d19eca219 10000.00000000 764 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": 737, "vin": [ { "gen": { "height": 727 } } ], "vout": [ { "amount": 2000000, "target": { "key": "f713083b37a3202f45ec124cf23e6ea239f1e2c5f321d64dfbf20f73c54a6565" } }, { "amount": 1000000000000, "target": { "key": "374232137adfcc49e70d46ffed572f7cf7c491c950f049230e45da4d19eca219" } } ], "extra": [ 1, 90, 160, 200, 61, 162, 30, 71, 191, 191, 34, 171, 156, 107, 0, 98, 187, 169, 6, 195, 13, 125, 193, 162, 142, 175, 12, 223, 123, 134, 199, 182, 207, 2, 8, 0, 0, 0, 0, 107, 96, 53, 179 ], "signatures": [ ] }


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