Autorefresh is OFF

Tx hash: 1b186275b3e478d48b1dfef80b3f3f43e714fc342888dd950a332d39b9d09942

Tx prefix hash: 1b186275b3e478d48b1dfef80b3f3f43e714fc342888dd950a332d39b9d09942
Tx public key: 8d4361881d1e10972c4d131a5a5a210ed378e764ec4f06d1a8709e1b1c9d1a19
Timestamp: 1517425093 Timestamp [UCT]: 2018-01-31 18:58:13 Age [y:d:h:m:s]: 04:112:13:46:57
Block: 734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1122859 RingCT/type: no
Extra: 018d4361881d1e10972c4d131a5a5a210ed378e764ec4f06d1a8709e1b1c9d1a19020800000000244f3d56

2 output(s) for total of 10000.02000000 TUBE

stealth address amount amount idx
00: 9bbbad768f94dbb41e39041411a8a487e332f9a83f8fddf8695fe2146515ab2b 0.02000000 106 of 151559
01: 56ec9fcfd93da90b563104913335df4faa3b271f5a6d182945cf8f9f63be5aca 10000.00000000 771 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": 744, "vin": [ { "gen": { "height": 734 } } ], "vout": [ { "amount": 2000000, "target": { "key": "9bbbad768f94dbb41e39041411a8a487e332f9a83f8fddf8695fe2146515ab2b" } }, { "amount": 1000000000000, "target": { "key": "56ec9fcfd93da90b563104913335df4faa3b271f5a6d182945cf8f9f63be5aca" } } ], "extra": [ 1, 141, 67, 97, 136, 29, 30, 16, 151, 44, 77, 19, 26, 90, 90, 33, 14, 211, 120, 231, 100, 236, 79, 6, 209, 168, 112, 158, 27, 28, 157, 26, 25, 2, 8, 0, 0, 0, 0, 36, 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