Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e162c5a9f853c95126aa70618cb33e0edd5a38cb875e9fb9c81a3fd3512251

Tx prefix hash: 750ba1b5b1c88841d797ec23210c7f900b30af8e91cb1a6975cac367edb7dcb4
Tx public key: 4707ba97d1ae010b70c3970b61fc961af54695f48cccd8e26c22c13aec9cc741
Timestamp: 1764322718 Timestamp [UCT]: 2025-11-28 09:38:38 Age [y:d:h:m:s]: 00:040:02:34:20
Block: 1421887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28720 RingCT/type: yes/0
Extra: 014707ba97d1ae010b70c3970b61fc961af54695f48cccd8e26c22c13aec9cc7410211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97927bb0c0949af5bfda04c2e84cf326dc26d404ea5adf370dac601b00cdcaeb 0.600000000000 1910450 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": 1421897, "vin": [ { "gen": { "height": 1421887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97927bb0c0949af5bfda04c2e84cf326dc26d404ea5adf370dac601b00cdcaeb" } } ], "extra": [ 1, 71, 7, 186, 151, 209, 174, 1, 11, 112, 195, 151, 11, 97, 252, 150, 26, 245, 70, 149, 244, 140, 204, 216, 226, 108, 34, 193, 58, 236, 156, 199, 65, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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