Beldex Blockchain Explorer

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

Tx hash: 880e916f2c31862977330ef535a970f10c808714ce5fe011c4127e0177769f90

Tx prefix hash: 27a8f1307ee2de9cea0b7823a0538ed2e256376bbf364ffcb6618ff3a323cc20
Tx public key: 91237733114df6d12d011fd72310ba48c24962fc6500084d396e235dad1420a1
Timestamp: 1552607312 Timestamp [UCT]: 2019-03-14 23:48:32 Age [y:d:h:m:s]: 00:006:07:01:49
Block: 29229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4615 RingCT/type: yes/0
Extra: 0191237733114df6d12d011fd72310ba48c24962fc6500084d396e235dad1420a1021100000009bb8ec600000000000000000000

1 output(s) for total of 0.001000000000 bdx

stealth address amount amount bdx
00: aa1c0642c59f597a7098ccbe584d21631a68529505d5c569331dd0a741f5577b 0.001000000000 47565 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": 29289, "vin": [ { "gen": { "height": 29229 } } ], "vout": [ { "amount": 1000000000, "target": { "key": "aa1c0642c59f597a7098ccbe584d21631a68529505d5c569331dd0a741f5577b" } } ], "extra": [ 1, 145, 35, 119, 51, 17, 77, 246, 209, 45, 1, 31, 215, 35, 16, 186, 72, 194, 73, 98, 252, 101, 0, 8, 77, 57, 110, 35, 93, 173, 20, 32, 161, 2, 17, 0, 0, 0, 9, 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