Beldex Blockchain Explorer

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

TX Hash: f709649d154655abe8fddf3ac3b4bf29e4dbe868c99b6c4dd9b54eb7df1d558a

TX Prefix Hash: e45c53cced6f1d731db6162f6f3b822977d2bd60caeacef0116958d27ec47f11

TX Public Key: 8aa9ec952a3c1c0729a41c0c014d69e54b195600aa458e9d501ed550bb131f75

Metadata

Timestamp: 1549871492 Timestamp [UCT]: 2019-02-11 07:51:32 Age [y:d:h:m:s]: 00:074:00:47:14
Block: 9322 Fee (Per kB): 0.000000000 (0.000000000) TX Size: 0.0977 kB
TX Version: 2 No Of Confirmations: 48253 RingCT/Type: Yes/0
Extra: 018aa9ec952a3c1c0729a41c0c014d69e54b195600aa458e9d501ed550bb131f75021100000004093e0800000000000000000000

Outputs

1 output(s) for total of 1.000000000 bdx

Stealth Address Amount Amount Index
00: 0ce5c7f43ba36c700260b57b1eaa00d8f833f93f582074ee4cadc59e38197b39 1.000000000 14203 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": 9382, "vin": [ { "gen": { "height": 9322 } } ], "vout": [ { "amount": 1000000000, "target": { "key": "0ce5c7f43ba36c700260b57b1eaa00d8f833f93f582074ee4cadc59e38197b39" } } ], "extra": [ 1, 138, 169, 236, 149, 42, 60, 28, 7, 41, 164, 28, 12, 1, 77, 105, 229, 75, 25, 86, 0, 170, 69, 142, 157, 80, 30, 213, 80, 187, 19, 31, 117, 2, 17, 0, 0, 0, 4, 9, 62, 8, 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