Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca1021527166045e33c962b4121e989858c7939cb87b19508c73f609ce3c9c61

Tx prefix hash: b8f2fdf1deb058f95705b379c8635cb624d33884d44e126722f8a50adb7b259b
Tx public key: a2e766bf5fa07eb097f4283d8e5d28ecdfcc39d9b134759efb7cece9dc69524e
Timestamp: 1752961648 Timestamp [UCT]: 2025-07-19 21:47:28 Age [y:d:h:m:s]: 00:112:18:46:29
Block: 1329094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79398 RingCT/type: yes/0
Extra: 01a2e766bf5fa07eb097f4283d8e5d28ecdfcc39d9b134759efb7cece9dc69524e021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a52cfef61a5f698d9fc8994d72a08e62cde2ddc5bd1703c216f7a5ca4ac4bce 0.600000000000 1816869 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": 1329104, "vin": [ { "gen": { "height": 1329094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a52cfef61a5f698d9fc8994d72a08e62cde2ddc5bd1703c216f7a5ca4ac4bce" } } ], "extra": [ 1, 162, 231, 102, 191, 95, 160, 126, 176, 151, 244, 40, 61, 142, 93, 40, 236, 223, 204, 57, 217, 177, 52, 117, 158, 251, 124, 236, 233, 220, 105, 82, 78, 2, 17, 0, 0, 0, 2, 228, 220, 144, 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