Autorefresh is OFF

Tx hash: beec1c4557adfe1a139f73127d2e7d7b8e4692063f5461cb4752054c666528b9

Tx prefix hash: beec1c4557adfe1a139f73127d2e7d7b8e4692063f5461cb4752054c666528b9
Tx public key: 2313c25369795896bc5a1e23bb6b5a97021adfec89b2c1396f0a11b8d98635f1
Timestamp: 1517480356 Timestamp [UCT]: 2018-02-01 10:19:16 Age [y:d:h:m:s]: 05:129:21:38:09
Block: 1539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1240 kB
Tx version: 1 No of confirmations: 1396807 RingCT/type: no
Extra: 012313c25369795896bc5a1e23bb6b5a97021adfec89b2c1396f0a11b8d98635f1020800000000268354b8

2 output(s) for total of 10000.00200000 TUBE

stealth address amount amount idx
00: 101e547721f7141edffe6643045165f68c3ea4859e87011bd4170a1c98ac5f16 0.00200000 960 of 58525
01: d6dc52b592228afb078c0f24da90a7b14ee7f44d21a7813fe1ed08af97c1e0fc 10000.00000000 1578 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": 1549, "vin": [ { "gen": { "height": 1539 } } ], "vout": [ { "amount": 200000, "target": { "key": "101e547721f7141edffe6643045165f68c3ea4859e87011bd4170a1c98ac5f16" } }, { "amount": 1000000000000, "target": { "key": "d6dc52b592228afb078c0f24da90a7b14ee7f44d21a7813fe1ed08af97c1e0fc" } } ], "extra": [ 1, 35, 19, 194, 83, 105, 121, 88, 150, 188, 90, 30, 35, 187, 107, 90, 151, 2, 26, 223, 236, 137, 178, 193, 57, 111, 10, 17, 184, 217, 134, 53, 241, 2, 8, 0, 0, 0, 0, 38, 131, 84, 184 ], "signatures": [ ] }


Less details
source code | explorer version (api): master-2020-03-09-0f3cc6b (1.1) | bittube version: 3.1.0.0-master-34dd77663