Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 595b47e98845b2f910ebf93df0cc4b6e1903b9ad6cf9f66f9f94cc0edb6a3ff4

Tx prefix hash: 6468cc796cf617bc42ea924215e8c687dba52686b67e8660466071d82c19f914
Tx public key: d940e1d12aedd221b0bdf214bdac99e0adc389ca4be33ba6ec99c13616d3e44b
Timestamp: 1755512721 Timestamp [UCT]: 2025-08-18 10:25:21 Age [y:d:h:m:s]: 00:095:13:40:27
Block: 1349123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68173 RingCT/type: yes/0
Extra: 01d940e1d12aedd221b0bdf214bdac99e0adc389ca4be33ba6ec99c13616d3e44b02110000000701491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d66051feaa6e7dc1e2a615ab66e14686dc4a8e5983d09e68db6cac99f51a1695 0.600000000000 1837054 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": 1349133, "vin": [ { "gen": { "height": 1349123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d66051feaa6e7dc1e2a615ab66e14686dc4a8e5983d09e68db6cac99f51a1695" } } ], "extra": [ 1, 217, 64, 225, 209, 42, 237, 210, 33, 176, 189, 242, 20, 189, 172, 153, 224, 173, 195, 137, 202, 75, 227, 59, 166, 236, 153, 193, 54, 22, 211, 228, 75, 2, 17, 0, 0, 0, 7, 1, 73, 31, 136, 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