Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250998f8ead2ba337765263ba08406f7e3c9e33a48be4fb5eb528fb63ecb524d

Tx prefix hash: 109dcafd8104ab5d5ad3f543dd992498b01833bd30ab7f76267633f64c21d54a
Tx public key: 2f5a1633057a666d71dc9ad6bcbc3c4b64f49994062b8a7ce07800abd530cb15
Timestamp: 1729622682 Timestamp [UCT]: 2024-10-22 18:44:42 Age [y:d:h:m:s]: 00:142:15:13:33
Block: 1137300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101749 RingCT/type: yes/0
Extra: 012f5a1633057a666d71dc9ad6bcbc3c4b64f49994062b8a7ce07800abd530cb15021100000001aa787773000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79591aeef22acddf0bdd4c3bb3036d3da8e8c248021f4a3c8eff752bdfaa0cbf 0.600000000000 1620763 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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": 1137310, "vin": [ { "gen": { "height": 1137300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79591aeef22acddf0bdd4c3bb3036d3da8e8c248021f4a3c8eff752bdfaa0cbf" } } ], "extra": [ 1, 47, 90, 22, 51, 5, 122, 102, 109, 113, 220, 154, 214, 188, 188, 60, 75, 100, 244, 153, 148, 6, 43, 138, 124, 224, 120, 0, 171, 213, 48, 203, 21, 2, 17, 0, 0, 0, 1, 170, 120, 119, 115, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8