Beldex Blockchain Explorer

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

TX Hash: 40ec6365d0eb05c5721c02dd98555d5e80fb667cf3fd8eef5eaa621b9cbf9bfb

TX Public Key: 5955f39373f76bb355ba939b9f8ac5be45a4fefe8e7fc5c4ab7dcdee17a5cc55


Timestamp: 1555338342 Timestamp [UCT]: 2019-04-15 14:25:42 Age [y:d:h:m:s]: 00:008:22:29:38
Block: 50777 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5716 RingCT/Type: Yes/0
Extra: 017737728eae27d2e7fd01ff7c782312789e82a03fb3600173a2fb0b40af7a5d8a020800000001b877b400015955f39373f76bb355ba939b9f8ac5be45a4fefe8e7fc5c4ab7dcdee17a5cc55720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 4492a8e5c810f7d7ffd1b4420816c01e37dc90db29e3e1dfe786b6c38dbe2170 1.000000000 77803 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