Autorefresh is OFF

Tx hash: 05abb10114eed22a4376e2f1e4f553870330fac2f86647b9c7fe26903197717a

Tx prefix hash: 05abb10114eed22a4376e2f1e4f553870330fac2f86647b9c7fe26903197717a
Tx public key: 0961114bf29f49161cb507e91cb613a33909c8c139c79eb427aad36c2004839e
Timestamp: 1517423528 Timestamp [UCT]: 2018-01-31 18:32:08 Age [y:d:h:m:s]: 05:057:03:37:32
Block: 712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1344952 RingCT/type: no
Extra: 010961114bf29f49161cb507e91cb613a33909c8c139c79eb427aad36c2004839e0208000000007e6035b3

2 output(s) for total of 10000.00300000 TUBE

stealth address amount amount idx
00: 21f8b8df610c41b3fb86040343bfcb394021768ed7843b45f9086078e3b4a86b 0.00300000 75 of 57727
01: a9c30f04e5f18fa7f932d3ae1f4c2675c34ab2b237ee94f73d2a539d3ad7267d 10000.00000000 749 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": 722, "vin": [ { "gen": { "height": 712 } } ], "vout": [ { "amount": 300000, "target": { "key": "21f8b8df610c41b3fb86040343bfcb394021768ed7843b45f9086078e3b4a86b" } }, { "amount": 1000000000000, "target": { "key": "a9c30f04e5f18fa7f932d3ae1f4c2675c34ab2b237ee94f73d2a539d3ad7267d" } } ], "extra": [ 1, 9, 97, 17, 75, 242, 159, 73, 22, 28, 181, 7, 233, 28, 182, 19, 163, 57, 9, 200, 193, 57, 199, 158, 180, 39, 170, 211, 108, 32, 4, 131, 158, 2, 8, 0, 0, 0, 0, 126, 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