Autorefresh is OFF

Tx hash: 456f4cf2bd89c2c37c9223bacc45d150e4bd9790bde4cd17282c9160111175d9

Tx prefix hash: 456f4cf2bd89c2c37c9223bacc45d150e4bd9790bde4cd17282c9160111175d9
Tx public key: 3fd68f8abef2fa62e64791579259ac27b92f1c61df870f003544365ba1605e0a
Timestamp: 1517411571 Timestamp [UCT]: 2018-01-31 15:12:51 Age [y:d:h:m:s]: 05:235:11:05:51
Block: 423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1473080 RingCT/type: no
Extra: 013fd68f8abef2fa62e64791579259ac27b92f1c61df870f003544365ba1605e0a020800000000056035b3

2 output(s) for total of 10000.00100000 TUBE

stealth address amount amount idx
00: 759a939c69f0fb9861a1a313fe92a484249a9c981028c8adda3a3ff8284b4d90 0.00100000 84 of 60494
01: 022ce2d3cf0dbda4019e020cd9f32c554c247d7b4645f10569241e8d3ce4228f 10000.00000000 438 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": 433, "vin": [ { "gen": { "height": 423 } } ], "vout": [ { "amount": 100000, "target": { "key": "759a939c69f0fb9861a1a313fe92a484249a9c981028c8adda3a3ff8284b4d90" } }, { "amount": 1000000000000, "target": { "key": "022ce2d3cf0dbda4019e020cd9f32c554c247d7b4645f10569241e8d3ce4228f" } } ], "extra": [ 1, 63, 214, 143, 138, 190, 242, 250, 98, 230, 71, 145, 87, 146, 89, 172, 39, 185, 47, 28, 97, 223, 135, 15, 0, 53, 68, 54, 91, 161, 96, 94, 10, 2, 8, 0, 0, 0, 0, 5, 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