Beldex Blockchain Explorer

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

TX Hash: 21caa0266e0b85fec88a7a1f62eab6d9fd73b1d714ffa1db54a3384bc95b53f2

TX Public Key: 0c0de95c87ee60aa040c12bf81bc1b11eddf9aab06081b1fade925e876e840b7

Metadata

Timestamp: 1555337840 Timestamp [UCT]: 2019-04-15 14:17:20 Age [y:d:h:m:s]: 00:008:22:37:38
Block: 50772 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1641 kB
TX Version: 2 No Of Confirmations: 5721 RingCT/Type: Yes/0
Extra: 019d137eb637c6c21aa9dabeaec1e37f434c145be41bd3d1713d0cf81a5b01f51b0211000000016a404f00000000000000000000010c0de95c87ee60aa040c12bf81bc1b11eddf9aab06081b1fade925e876e840b7720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 0a43188aaea07087aa1052b09b35f684cc4c74e26756a057cdc50cb09341b3a2 1.000000000 77779 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