Beldex Blockchain Explorer

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

TX Hash: c135b1f88ba35ba6cb4e292cfdcbf94cfc4c20a18680530c487e14e6f1e7fb1f

TX Public Key: cce5e4aef041b2f80838440ec77049e4879a2968b3950222184f350169ed8f53

Metadata

Timestamp: 1555338554 Timestamp [UCT]: 2019-04-15 14:29:14 Age [y:d:h:m:s]: 00:008:22:22:37
Block: 50779 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1641 kB
TX Version: 2 No Of Confirmations: 5714 RingCT/Type: Yes/0
Extra: 01810a440273a6ab73ccc5594992e169534f0c04f1c7978bf05307cd206c9ccae1021100000001b3405f0000000000000000000001cce5e4aef041b2f80838440ec77049e4879a2968b3950222184f350169ed8f53720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: be749eda8773aec777f932ba36107d01c4b733bd5238ca40b338296579fe401e 1.000000000 77805 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