Beldex Blockchain Explorer

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

TX Hash: 12f569e08c211397fbfdb5065d6ce9acfd1c956bbae52a7c055aa4b0fa956d9b

TX Public Key: 46849b3c0be0f6dcc52869f2dfbac88e9c066c2f99dd3c4a65c70c74aa78f538


Timestamp: 1555338065 Timestamp [UCT]: 2019-04-15 14:21:05 Age [y:d:h:m:s]: 00:008:22:36:15
Block: 50774 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1641 kB
TX Version: 2 No Of Confirmations: 5719 RingCT/Type: Yes/0
Extra: 01b382475e41425a0e4e2080d16603867735f806b713213b62b6f35186441e862402110000000589abc5000000000000000000000146849b3c0be0f6dcc52869f2dfbac88e9c066c2f99dd3c4a65c70c74aa78f538720000000000000000000000000000000000000000000000000000000000000000


1 output(s) for total of 1.020000000 bdx

Stealth Address Amount Amount Index
00: d048da0e8886da0e2f3db2d2960379124bac724e18e24372ea35615f033dfe7a 1.020000000 77781 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