Autorefresh is OFF

Tx hash: e189f6463b83dd1dcf89aa7e9d9a3151abe031585e49444abd2d57de99a6d671

Tx prefix hash: e189f6463b83dd1dcf89aa7e9d9a3151abe031585e49444abd2d57de99a6d671
Tx public key: 4404a71d136807dc3f49161d123b6d3a096461ab451a24afaad3151d192dad9f
Timestamp: 1517439278 Timestamp [UCT]: 2018-01-31 22:54:38 Age [y:d:h:m:s]: 04:312:11:12:36
Block: 1030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1250 kB
Tx version: 1 No of confirmations: 1266056 RingCT/type: no
Extra: 014404a71d136807dc3f49161d123b6d3a096461ab451a24afaad3151d192dad9f020800000000c16035b3

2 output(s) for total of 10000.06000000 TUBE

stealth address amount amount idx
00: c64efcac170cd321d31a6ea4949c431eb829f96569909c072e5a80ff9db2fae7 0.06000000 247 of 134730
01: ac6c38bf847d679ddeb257507d5ea2b1d8eed88cf0d84c98195f1ef43614cc73 10000.00000000 1068 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": 1040, "vin": [ { "gen": { "height": 1030 } } ], "vout": [ { "amount": 6000000, "target": { "key": "c64efcac170cd321d31a6ea4949c431eb829f96569909c072e5a80ff9db2fae7" } }, { "amount": 1000000000000, "target": { "key": "ac6c38bf847d679ddeb257507d5ea2b1d8eed88cf0d84c98195f1ef43614cc73" } } ], "extra": [ 1, 68, 4, 167, 29, 19, 104, 7, 220, 63, 73, 22, 29, 18, 59, 109, 58, 9, 100, 97, 171, 69, 26, 36, 175, 170, 211, 21, 29, 25, 45, 173, 159, 2, 8, 0, 0, 0, 0, 193, 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