Beldex Blockchain Explorer

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

TX Hash: 97d4deb0657afc1a86bc21b3372bcaab09d9f57a5f4960caf3421d90caca4c7d

TX Public Key: 86f83c3ec98a72aa086b76e9025d7df74414c3882352a5eb95bddbd4bc0014cf


Timestamp: 1555397046 Timestamp [UCT]: 2019-04-16 06:44:06 Age [y:d:h:m:s]: 00:008:06:08:00
Block: 51267 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5226 RingCT/Type: Yes/0
Extra: 01409a6a93496de96c2a10bddd0ad64e70b9609dd93a4150c8edbd3400af6f471e020800000006267ce7000186f83c3ec98a72aa086b76e9025d7df74414c3882352a5eb95bddbd4bc0014cf720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.276000000 bdx

Stealth Address Amount Amount Index
00: bec1f55bd3e5e2459a175dda838645d2ecefb43df950bc9eaf993cc107c6e252 1.276000000 78478 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