Beldex Blockchain Explorer

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

TX Hash: 8a55e5f9b027d6d9d584905e44e75ea0e8c073f7d0c1173bd6cc0f47d5c2b348

TX Public Key: 580b2c87ea5d7a336735e84c6071a886e08c92ad05625bf11cd562ff56ca6f88


Timestamp: 1555397115 Timestamp [UCT]: 2019-04-16 06:45:15 Age [y:d:h:m:s]: 00:008:06:07:36
Block: 51268 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5225 RingCT/Type: Yes/0
Extra: 011c044541f0036025e067be57d8032a2f407a49f23667b7c2e8fa4d85639465d0020800000005dcfefe0001580b2c87ea5d7a336735e84c6071a886e08c92ad05625bf11cd562ff56ca6f88720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: a50297fee704289935ff4d9b11af4af090547cabe3dc4048eb7de10676ce8437 1.000000000 78491 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