Beldex Blockchain Explorer

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

TX Hash: 3ecb3c255e2f418a1d1476f3e136e10dc32838dd2f12476b6b00896ff2ef7c30

TX Public Key: 3bac9b3a7d2529530159ec131b53ec956cbd950d051ff074e513bd372ac36a3e

Metadata

Timestamp: 1549871807 Timestamp [UCT]: 2019-02-11 07:56:47 Age [y:d:h:m:s]: 00:072:04:57:42
Block: 9328 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1416 kB
TX Version: 2 No Of Confirmations: 47165 RingCT/Type: Yes/0
Extra: 013bac9b3a7d2529530159ec131b53ec956cbd950d051ff074e513bd372ac36a3e032100efa0f945774d67bd7319c4b0d276b79123bb79dc0551c0e539200aa51a755b6e021b00000000000000000000000000047c28ef00000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 99c48f7dcb5529b8b6cffcd1aeee0d9d83f32d537c4ed7c0ae940fad971de447 1.000000000 14216 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