Beldex Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Tx hash: 8aae9ce49355ac626bedba9ef1c367894ea58d5adc295a1d32c0749878736384

Tx prefix hash: b729d345fc529b597882921c3c9116a615f302607b76e4a1f7e8609ff8b4c551
Tx public key: 5b342873e7089e9c1763f99d2df3819dfacc6d0e3455ccc6daac68259db493cd
Timestamp: 1549871566 Timestamp [UCT]: 2019-02-11 07:52:46 Age [y:d:h:m:s]: 00:008:08:00:46
Block: 9324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 4051 RingCT/type: yes/0
Extra: 015b342873e7089e9c1763f99d2df3819dfacc6d0e3455ccc6daac68259db493cd021100000002fdd0e000000000000000000000

1 output(s) for total of 0.001000000000 bdx

stealth address amount amount idx
00: 1fa2cdafd3394196020352616e6848f2507879560ff3a9dca59a0781e076f75c 0.001000000000 14207 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": 9384, "vin": [ { "gen": { "height": 9324 } } ], "vout": [ { "amount": 1000000000, "target": { "key": "1fa2cdafd3394196020352616e6848f2507879560ff3a9dca59a0781e076f75c" } } ], "extra": [ 1, 91, 52, 40, 115, 231, 8, 158, 156, 23, 99, 249, 157, 45, 243, 129, 157, 250, 204, 109, 14, 52, 85, 204, 198, 218, 172, 104, 37, 157, 180, 147, 205, 2, 17, 0, 0, 0, 2, 253, 208, 224, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2019-02-09-6115f5e (1.1) | monero version: 0.1-a343c80