Autorefresh is OFF

Tx hash: 7b29bde72b3e6472eaba6489def346948a3ee6fb76c32d882ff4db387ac3e85e

Tx prefix hash: 7b29bde72b3e6472eaba6489def346948a3ee6fb76c32d882ff4db387ac3e85e
Tx public key: 46f539f9e9b39f5978320f60a17626d5d3ebd3e83860a916f0700f4101f42e30
Timestamp: 1517419393 Timestamp [UCT]: 2018-01-31 17:23:13 Age [y:d:h:m:s]: 02:305:16:45:16
Block: 621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 743400 RingCT/type: no
Extra: 0146f539f9e9b39f5978320f60a17626d5d3ebd3e83860a916f0700f4101f42e30020800000001666035b3

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 92c161c55562b2261d0e3663311e031b7862756807ef478e00ed1e2f9aa7709e 0.00200000 60 of 58525
01: f5373b3567c7f662b7d8e9c14001c053ef7dffb006a9f7e021762aaa6ed0d366 10000.00000000 654 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": 631, "vin": [ { "gen": { "height": 621 } } ], "vout": [ { "amount": 200000, "target": { "key": "92c161c55562b2261d0e3663311e031b7862756807ef478e00ed1e2f9aa7709e" } }, { "amount": 1000000000000, "target": { "key": "f5373b3567c7f662b7d8e9c14001c053ef7dffb006a9f7e021762aaa6ed0d366" } } ], "extra": [ 1, 70, 245, 57, 249, 233, 179, 159, 89, 120, 50, 15, 96, 161, 118, 38, 213, 211, 235, 211, 232, 56, 96, 169, 22, 240, 112, 15, 65, 1, 244, 46, 48, 2, 8, 0, 0, 0, 1, 102, 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