Beldex Blockchain Explorer

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

TX Hash: f142765914502a87ba58fff37ff50ebca9348463e4ace9e10e91544bb38b8a79

TX Public Key: 0119bb02e67a6aa815250cd2049d3ea06d188720fdf73d029f9695a646ba0e62


Timestamp: 1555396511 Timestamp [UCT]: 2019-04-16 06:35:11 Age [y:d:h:m:s]: 00:008:06:17:27
Block: 51264 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5229 RingCT/Type: Yes/0
Extra: 01ff563ad85200d67b74feafec5f10a2261a54519bb229ac95a3d19a83da556695020800000002dcfefe00010119bb02e67a6aa815250cd2049d3ea06d188720fdf73d029f9695a646ba0e62720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 9127eeb35f757ac94e259965221c9106345bf655523df3a9e4b46f8f09c07e95 1.000000000 78475 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