Beldex Blockchain Explorer

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

TX Hash: 56134dc57903f48382e244868748898cc78c2d4d9914223c6fe411bcf92d7d0f

TX Public Key: b2c7cdde203c00e6782813f6bdb6ba9f8a13c655d7f89eadf2a751d9c77fb7a7

Metadata

Timestamp: 1555395997 Timestamp [UCT]: 2019-04-16 06:26:37 Age [y:d:h:m:s]: 00:008:06:25:29
Block: 51261 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.1553 kB
TX Version: 2 No Of Confirmations: 5232 RingCT/Type: Yes/0
Extra: 01c2e40b51445a8109f8ec7893f9768b96993f34707ee3c410aa3b46ff832c4c15020800000006b3ac620001b2c7cdde203c00e6782813f6bdb6ba9f8a13c655d7f89eadf2a751d9c77fb7a7720000000000000000000000000000000000000000000000000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: bb88671b896305cb92c3e9204178111599e25378544e8e3aa4560f32c664fab5 1.000000000 78472 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