Beldex Blockchain Explorer

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

TX Hash: 16456de27639974987eefd2556d4354df33ca74a89af64d315c347bce85dfb5a

TX Public Key: 06289b70725842cc8eae9ec61af9ea5f9a31f53adc5087dcf16a0bfe692a0ae9


Timestamp: 1549872121 Timestamp [UCT]: 2019-02-11 08:02:01 Age [y:d:h:m:s]: 00:072:04:54:52
Block: 9329 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1416 kB
TX Version: 2 No Of Confirmations: 47164 RingCT/Type: Yes/0
Extra: 0106289b70725842cc8eae9ec61af9ea5f9a31f53adc5087dcf16a0bfe692a0ae9032100ea6201aa60d846ea5844c4073e67cde1849396fdcea7ae2aa2a8042095a5c123021b00000000000000000000000000267c28ef00000000000000000000


1 output(s) for total of 1.001120000 bdx

Stealth Address Amount Amount Index
00: f6d6ff3035b1c43af3c6e8347fd8fc57c2df6cacf2c27f90a4baad8904890bd9 1.001120000 14217 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