Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c20640322eaffb7e6fc1c40b4671142f740f071714998aff89e006398868a51

Tx prefix hash: cbf1590e1e6197904a2c7cb6b8ef2ebfb031277233b0bc4ef04ae56db0bfe8a3
Tx public key: 72fe7bf9eef82e07196df0b60a12f515ddb1dc03c93ee5122b44725653b438c7
Timestamp: 1754906297 Timestamp [UCT]: 2025-08-11 09:58:17 Age [y:d:h:m:s]: 00:108:19:54:38
Block: 1344732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77040 RingCT/type: yes/0
Extra: 0172fe7bf9eef82e07196df0b60a12f515ddb1dc03c93ee5122b44725653b438c7021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53eb8cc9d58a7528cb79d8c3287abf39dbfa4af65a22e1cb77a2b546e521aa99 0.600000000000 1832617 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": 1344742, "vin": [ { "gen": { "height": 1344732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53eb8cc9d58a7528cb79d8c3287abf39dbfa4af65a22e1cb77a2b546e521aa99" } } ], "extra": [ 1, 114, 254, 123, 249, 238, 248, 46, 7, 25, 109, 240, 182, 10, 18, 245, 21, 221, 177, 220, 3, 201, 62, 229, 18, 43, 68, 114, 86, 83, 180, 56, 199, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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