Beldex Blockchain Explorer

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

TX Hash: d21d338c5701e4424e6b9b30c4cb3a3d5cc3157722b04c242170539cfed1c537

TX Public Key: c545f45e71b01ee64dcea906ef47ad75c13d58a05d4871c950f76d5aaa134e69

Metadata

Timestamp: 1555338269 Timestamp [UCT]: 2019-04-15 14:24:29 Age [y:d:h:m:s]: 00:008:22:29:37
Block: 50776 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5717 RingCT/Type: Yes/0
Extra: 01225298407fc2eb31a83b716355fbabe41e732afbeadb5b380595ed1c1d2bbf71020800000005fda9930001c545f45e71b01ee64dcea906ef47ad75c13d58a05d4871c950f76d5aaa134e69720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.400000000 bdx

Stealth Address Amount Amount Index
00: 193290d46892c153133ce6c15941b32f4f8cbfeef5bb3c32c36018c703ead783 1.400000000 77787 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