Beldex Blockchain Explorer

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

TX Hash: bb928ec571b9d5172f6db1b7a5fc606edfc258d5526149b82aedeaa7b01c3bc7

TX Prefix Hash: eef02c1df3750b787961f523dd41f2911631fca49cb18134bd80becdb0261cfe

TX Public Key: fab231e1bfebd86f0c3baa1dc66e4ec1bcf1950f5f2c4a3932fcae9b701fd495

Metadata

Timestamp: 1549871782 Timestamp [UCT]: 2019-02-11 07:56:22 Age [y:d:h:m:s]: 00:074:00:42:24
Block: 9327 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.0977 kB
TX Version: 2 No Of Confirmations: 48248 RingCT/Type: Yes/0
Extra: 01fab231e1bfebd86f0c3baa1dc66e4ec1bcf1950f5f2c4a3932fcae9b701fd4950211000000012523f500000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 093cb5e80a9692777df9b5b0c5ace7da0860a08cdeb09031161cd30e5ad201a5 1.000000000 14215 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




{ "version": 2, "unlock_time": 9387, "vin": [ { "gen": { "height": 9327 } } ], "vout": [ { "amount": 1000000000, "target": { "key": "093cb5e80a9692777df9b5b0c5ace7da0860a08cdeb09031161cd30e5ad201a5" } } ], "extra": [ 1, 250, 178, 49, 225, 191, 235, 216, 111, 12, 59, 170, 29, 198, 110, 78, 193, 188, 241, 149, 15, 95, 44, 74, 57, 50, 252, 174, 155, 112, 31, 212, 149, 2, 17, 0, 0, 0, 1, 37, 35, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less Details

Source Code | Explorer Version (api): master-2019-04-10-aec26a9 (1.1) | Beldex Version: 3.1.3-75fc9eb