Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddef114a085b8b873702b869ab9f9f38e28e04de4527631086aada766b852255

Tx prefix hash: a4636cb29be4b3f6982ce334985f75dd10a497daad8300c8c2ec31ec2f1f9f47
Tx public key: 7cfe2b94c4e42384e9cc60c1435c9df61e2c8c6fc378e717af60291a52192a10
Timestamp: 1742595444 Timestamp [UCT]: 2025-03-21 22:17:24 Age [y:d:h:m:s]: 00:254:01:31:12
Block: 1244404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179344 RingCT/type: yes/0
Extra: 017cfe2b94c4e42384e9cc60c1435c9df61e2c8c6fc378e717af60291a52192a10021100000003ca0c97f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d6b290f48ec6349e5c638f80d3c9abbb9ec42c115c93a616c3fa222a210de50 0.600000000000 1731395 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": 1244414, "vin": [ { "gen": { "height": 1244404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d6b290f48ec6349e5c638f80d3c9abbb9ec42c115c93a616c3fa222a210de50" } } ], "extra": [ 1, 124, 254, 43, 148, 196, 228, 35, 132, 233, 204, 96, 193, 67, 92, 157, 246, 30, 44, 140, 111, 195, 120, 231, 23, 175, 96, 41, 26, 82, 25, 42, 16, 2, 17, 0, 0, 0, 3, 202, 12, 151, 245, 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