Beldex Blockchain Explorer

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

TX Hash: 8fae2f9d6404c5ec124c437b25fa14763d98f7e3a08d051045ac12e995f20b57

TX Public Key: 6e1bc390c3d1117c5c35ae9c973470727f831df4311b3270a000f87ffff67510


Timestamp: 1555397541 Timestamp [UCT]: 2019-04-16 06:52:21 Age [y:d:h:m:s]: 00:008:06:02:37
Block: 51269 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5224 RingCT/Type: Yes/0
Extra: 01030dc5eb17dded57f5e8780f92ff242b752ccbe7e648bc916861cba0e8158788020800000004b3ac6200016e1bc390c3d1117c5c35ae9c973470727f831df4311b3270a000f87ffff67510720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 3b08c9da1cf6231559d7a2f30c19d3e118c40e6773c21fde30fe7447952000ec 1.000000000 78492 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