Beldex Blockchain Explorer

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

TX Hash: 44545dffaf29225d60939b1023b857bb1ffa9ac7f70559e134c5a53848bb1ab8

TX Public Key: 2fbda353c02dc4259fafe942657359f6072d82459b557bc221b97957290fe9df


Timestamp: 1549871667 Timestamp [UCT]: 2019-02-11 07:54:27 Age [y:d:h:m:s]: 00:072:04:58:24
Block: 9326 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1416 kB
TX Version: 2 No Of Confirmations: 47167 RingCT/Type: Yes/0
Extra: 012fbda353c02dc4259fafe942657359f6072d82459b557bc221b97957290fe9df032100a062d9a3f3bfd3e79c626f3356701abfc11e6073bdb1f0e6e964d17c82e672f5021b00000000000000000000000000040228e200000000000000000000


1 output(s) for total of 1.001360000 bdx

Stealth Address Amount Amount Index
00: f4df095b98a706cf7f5dc7b24c4baec64ea09cc69226e152eba13e01a2f7026a 1.001360000 14209 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