Beldex Blockchain Explorer

(No Javascript | No Cookies | No Web Analytics Trackers | No Images | Open Sourced)

TX Hash: 1e2ce27cd3ef305761886ad5ba67ae2cd5c9e6d0d0ac983e1dfef5a5d03a6008

TX Public Key: 673ab57910da53d5561523c44c44bb9359f3c7a26202f8ba5a74b701b6f7e990

Metadata

Timestamp: 1555396066 Timestamp [UCT]: 2019-04-16 06:27:46 Age [y:d:h:m:s]: 00:008:06:27:27
Block: 51262 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5231 RingCT/Type: Yes/0
Extra: 01abfd8f6ad1ae2b7d3acdbb15ac85101d56d60ba4ade4e7e08641e4ecaac22d61020800000006b3ac620001673ab57910da53d5561523c44c44bb9359f3c7a26202f8ba5a74b701b6f7e990720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 2c6a04b955e02f8ee5ffaa9d20c31070cbafdf5345e34b3382dcb89e6b5ff497 1.000000000 78473 of 0

Check which outputs belong to given Beldex 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 Beldex in this transaction

TX private key can be obtained using get_tx_key command in beldex-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




More Details

Source Code | Explorer Version (api): master-2019-04-10-aec26a9 (1.1) | Beldex Version: 3.1.3-75fc9eb