Beldex Blockchain Explorer

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

TX Hash: 4c3489645e0a69d40150213ba5838fa161524bc194b0724a882bc85ea0479229

TX Public Key: c552510d6071340eb94ffd4f3c5bb7998138d1e9b2675f759e7fe364a42477a1


Timestamp: 1555395981 Timestamp [UCT]: 2019-04-16 06:26:21 Age [y:d:h:m:s]: 00:008:06:29:24
Block: 51260 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5233 RingCT/Type: Yes/0
Extra: 01d3a173ee1121c1078869de874a2bc10de0ba28add019e8984dd57abd2228cd39020800000006267ce70001c552510d6071340eb94ffd4f3c5bb7998138d1e9b2675f759e7fe364a42477a1720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 486f1ecd8146a46f6f673e75441886cc71496850c783cd4973a3dae132158a8b 1.000000000 78471 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