Beldex Blockchain Explorer

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

TX Hash: e9cb9c93e41ed4a6634ffa7b13ddfd5ddafc717a4febbcd5947d98389dd161d7

TX Public Key: 310041869bf1a5ef13a5a03012bd52c98567253fd45931b296d5580e24b62eb7


Timestamp: 1555396529 Timestamp [UCT]: 2019-04-16 06:35:29 Age [y:d:h:m:s]: 00:008:06:17:22
Block: 51265 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5228 RingCT/Type: Yes/0
Extra: 01c42d9443a6b364b2a2b600fbf97fda8db9a9001ac9f244b1e1c11b795fb889a3020800000006267ce70001310041869bf1a5ef13a5a03012bd52c98567253fd45931b296d5580e24b62eb7720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 6197fdc5a6b0e2691c7b809e4b7a10f53bc552bd8d47932e2bb60dce2030ad33 1.000000000 78476 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