Beldex Blockchain Explorer

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

TX Hash: cfbbcf55f78348c0e5bd4d83cb6e4cdc7a0d8584a31c920e96e6e244cd9d4e82

TX Prefix Hash: 4042aed72c78e49556c9f745910f484983c9c0908b91497a527991084f21a1d3

TX Public Key: b097dee7c9a794c3a19631df74d9b41bac00d538d9a487a426d1f739b59dfb7b

Metadata

Timestamp: 1552607444 Timestamp [UCT]: 2019-03-14 23:50:44 Age [y:d:h:m:s]: 00:065:19:48:16
Block: 29232 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.0996 kB
TX Version: 2 No Of Confirmations: 44415 RingCT/Type: Yes/0
Extra: 01b097dee7c9a794c3a19631df74d9b41bac00d538d9a487a426d1f739b59dfb7b021100000009004fd100000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: de9fc20c41f2ff0f33f7a6539efd5b240adec17973696a3fb7f0316abdb02848 1.000000000 47568 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": 29292, "vin": [ { "gen": { "height": 29232 } } ], "vout": [ { "amount": 1000000000, "target": { "key": "de9fc20c41f2ff0f33f7a6539efd5b240adec17973696a3fb7f0316abdb02848" } } ], "extra": [ 1, 176, 151, 222, 231, 201, 167, 148, 195, 161, 150, 49, 223, 116, 217, 180, 27, 172, 0, 213, 56, 217, 164, 135, 164, 38, 209, 247, 57, 181, 157, 251, 123, 2, 17, 0, 0, 0, 9, 0, 79, 209, 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