Beldex Blockchain Explorer

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

Tx hash: 2f86266767727b39bfb7f7aa9a1382b20e7963b9135c4cc8c3c6e8261326a9a5

Tx prefix hash: 360b38887d7d96155e3929046505bc00b5c595cdd840b1e6b60790c73d424484
Tx public key: 8debe7c03db2530ba58f32c36ad0628e083512eb23ec2308d0ef5f2e085a513b
Timestamp: 1552607378 Timestamp [UCT]: 2019-03-14 23:49:38 Age [y:d:h:m:s]: 00:006:07:00:43
Block: 29230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4614 RingCT/type: yes/0
Extra: 018debe7c03db2530ba58f32c36ad0628e083512eb23ec2308d0ef5f2e085a513b021100000007bb8ec600000000000000000000

1 output(s) for total of 0.001000000000 bdx

stealth address amount amount bdx
00: a77e8e01099a972670904ff9821bd0d33b53cc026525266b64e12d1c44564f3e 0.001000000000 47566 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": 29290, "vin": [ { "gen": { "height": 29230 } } ], "vout": [ { "amount": 1000000000, "target": { "key": "a77e8e01099a972670904ff9821bd0d33b53cc026525266b64e12d1c44564f3e" } } ], "extra": [ 1, 141, 235, 231, 192, 61, 178, 83, 11, 165, 143, 50, 195, 106, 208, 98, 142, 8, 53, 18, 235, 35, 236, 35, 8, 208, 239, 95, 46, 8, 90, 81, 59, 2, 17, 0, 0, 0, 7, 187, 142, 198, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2019-03-12-347eb40 (1.1) | beldex version: 0.1-a343c80