Beldex Blockchain Explorer

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

TX Hash: 5e149983fab303fc849eb424b57601e1b5a48ce4844de81027b2213c7f103946

TX Public Key: a21df3e652802e685161a351adc5b9b98d711322d869857d27d29e0a6ca6a236

Metadata

Timestamp: 1555338174 Timestamp [UCT]: 2019-04-15 14:22:54 Age [y:d:h:m:s]: 00:008:22:33:09
Block: 50775 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5718 RingCT/Type: Yes/0
Extra: 01e0d59205b41dd311218bcbacdfe830043108496e62f786c7fc31a86fd91aaae0020800000006fe0a170001a21df3e652802e685161a351adc5b9b98d711322d869857d27d29e0a6ca6a236720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 953697e702f2ab74ff65f91eec0c40c8891c33d83edbf412b292c7a164b91148 1.000000000 77786 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