Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a70ef1cf5681a981046667b29465a3d0888f285cdfc321af3a7c9c0d7e0511a

Tx prefix hash: 4014de961292dfc544c447ed3dc96d6df9fb5811a4a75281054d7a3e290d644a
Tx public key: 94ed30afd214b4b4e9155596cbdd3c209f528b8f51bb2512d9a79053530f0a51
Timestamp: 1766274236 Timestamp [UCT]: 2025-12-20 23:43:56 Age [y:d:h:m:s]: 00:000:07:06:34
Block: 1438067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206 RingCT/type: yes/0
Extra: 0194ed30afd214b4b4e9155596cbdd3c209f528b8f51bb2512d9a79053530f0a510211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc941616fb1255aea944594aba8f9aa3742fc8352b565de7053c28fe461d7ee0 0.600000000000 1926882 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": 1438077, "vin": [ { "gen": { "height": 1438067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc941616fb1255aea944594aba8f9aa3742fc8352b565de7053c28fe461d7ee0" } } ], "extra": [ 1, 148, 237, 48, 175, 210, 20, 180, 180, 233, 21, 85, 150, 203, 221, 60, 32, 159, 82, 139, 143, 81, 187, 37, 18, 217, 167, 144, 83, 83, 15, 10, 81, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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