Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335d63a0a0ec07b80cd7290d57cb8565099ee2c4f4c308915f2bb02275cf97c5

Tx prefix hash: 7513bc146081a4df0a765ed1b80e90e5cd1193fa115787c246356a7be214a91f
Tx public key: d302ac1b41f1e89225500fecad6a6cb6ac63e1f8448d22a491d9198df0fdab80
Timestamp: 1761266175 Timestamp [UCT]: 2025-10-24 00:36:15 Age [y:d:h:m:s]: 00:017:07:01:24
Block: 1396568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12369 RingCT/type: yes/0
Extra: 01d302ac1b41f1e89225500fecad6a6cb6ac63e1f8448d22a491d9198df0fdab800211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 364b6303391e86044e1470af5cd1f31eb8a8a01c6c9d580e42b33f79989e3aee 0.600000000000 1884855 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": 1396578, "vin": [ { "gen": { "height": 1396568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "364b6303391e86044e1470af5cd1f31eb8a8a01c6c9d580e42b33f79989e3aee" } } ], "extra": [ 1, 211, 2, 172, 27, 65, 241, 232, 146, 37, 80, 15, 236, 173, 106, 108, 182, 172, 99, 225, 248, 68, 141, 34, 164, 145, 217, 25, 141, 240, 253, 171, 128, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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