Beldex Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Tx hash: d78314029a435cdfa691b3aa3eed0e6c33e5b65e8e806f49abcab780aed925a3

Tx public key: 1689ffc08c5a6c18f26743c3ae22d2bb908c0252cbf6c7379bdfe850f969af2f
Timestamp: 1549871605 Timestamp [UCT]: 2019-02-11 07:53:25 Age [y:d:h:m:s]: 00:008:08:03:33
Block: 9325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1416 kB
Tx version: 2 No of confirmations: 4053 RingCT/type: yes/0
Extra: 011689ffc08c5a6c18f26743c3ae22d2bb908c0252cbf6c7379bdfe850f969af2f03210035aa0c774472f83512cb09360c88149f04de1992848f7f9096d093e8361f2af7021b00000000000000000000000000037c28ef00000000000000000000

1 output(s) for total of 0.001000000000 bdx

stealth address amount amount idx
00: 047c22b616e041a8fe29ed894919e84741b8bf919ee8f1a0943c4b950325a744 0.001000000000 14208 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-02-09-6115f5e (1.1) | monero version: 0.1-a343c80