Beldex Blockchain Explorer

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

TX Hash: 1613347a398bf36ac4ec98512dfb93da8e9dca6113046c195dc8c49df7a6572d

TX Public Key: 2b7641049c039d8cbeeb7b47b5517ddc52465b400b36d682630ab5b10ac161f8


Timestamp: 1555396494 Timestamp [UCT]: 2019-04-16 06:34:54 Age [y:d:h:m:s]: 00:008:06:22:18
Block: 51263 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5230 RingCT/Type: Yes/0
Extra: 01d0e98d67334ec5096f9660db7b58ebacbe0eeab7f57f02ad617caa16b2f367b6020800000002b3ac6200012b7641049c039d8cbeeb7b47b5517ddc52465b400b36d682630ab5b10ac161f8720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 488e006cad14a44bd8ea3f99b6a1483549e926686e7633ee374f0ce7e318fecc 1.000000000 78474 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