Beldex Blockchain Explorer

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

TX Hash: b0acc653d09f51aedd549b24e5670c8e516efe3e2a360d20cef3ab3a74e1434b

TX Public Key: f9bf344a0738324e5f19c798801b637f83363896a3524f0816082bc06503d8e4


Timestamp: 1555395951 Timestamp [UCT]: 2019-04-16 06:25:51 Age [y:d:h:m:s]: 00:008:06:25:00
Block: 51259 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5233 RingCT/Type: Yes/0
Extra: 01dddb40982db42d1a267635be919caf61e0dcd9cf9fcba3fb54fa8514592ed84d020800000006267ce70001f9bf344a0738324e5f19c798801b637f83363896a3524f0816082bc06503d8e4720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 8cb02aa3f6c73abe97ee42f6de6f8f3befb8f30018757863bbfa4d40deba6dfe 1.000000000 78470 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