Beldex Blockchain Explorer

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

TX Hash: c705a4c6c95fa506bd0e526ba7e8a543301f9d0dc16bdc8b78ad931f5d45b159

TX Public Key: 7ff981fbfb7575b19bd018a7894c4e7e2e20fef8a72763e632c55f161182aecf

Metadata

Timestamp: 1555396612 Timestamp [UCT]: 2019-04-16 06:36:52 Age [y:d:h:m:s]: 00:008:06:19:33
Block: 51266 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5227 RingCT/Type: Yes/0
Extra: 01769fb87f335676ac49172a81843959522baeda751c236a3105bbe418262c93a5020800000006b3ac6200017ff981fbfb7575b19bd018a7894c4e7e2e20fef8a72763e632c55f161182aecf720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 5855deb00796782a8d4c858243361116c294e5547f328f863acb8be7704019c0 1.000000000 78477 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