Beldex Blockchain Explorer

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

TX Hash: ca230c35b5b9a487f1c3ac7603b1cc5d96775f244956f09baae5b3d157b2d5f1

TX Public Key: 71f200e7711b28ff1cf5c16f6bb28764367560051827e8baf81cc0ed6c10dfb5


Timestamp: 1555337804 Timestamp [UCT]: 2019-04-15 14:16:44 Age [y:d:h:m:s]: 00:008:22:34:07
Block: 50771 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5722 RingCT/Type: Yes/0
Extra: 01a3b1b9c6a0d7eb744e24c753fbfd968bae01adb8ac17be5d849cd5df8b538cb2020800000005fda993000171f200e7711b28ff1cf5c16f6bb28764367560051827e8baf81cc0ed6c10dfb5720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 4ec8543efd48941a419d6e546e810b93f94744168472b41de5a7a2d4837edbd6 1.000000000 77778 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