Beldex Blockchain Explorer

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

TX Hash: aa95c160cc14d194e7fe4049aeee57ea54d3d9b9008db3bb11e34f5f3f4c7fd9

TX Public Key: 1288d9104a95b4046ac2c6043a39f54bfdb74c38181a8ea59e8023f2eec8cbae


Timestamp: 1555338425 Timestamp [UCT]: 2019-04-15 14:27:05 Age [y:d:h:m:s]: 00:008:22:25:46
Block: 50778 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5715 RingCT/Type: Yes/0
Extra: 01b7b4392217bad086510cb788f0fe1cec2338c229329489dbe376a5c19aa73537020800000005fda99300011288d9104a95b4046ac2c6043a39f54bfdb74c38181a8ea59e8023f2eec8cbae720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 06e05b824c2afe2bef18ee723819ac22172ba0705c6b18d64609d7759d11636b 1.000000000 77804 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