Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd48010cd270209ae78b6f8715c7ee1a563fbdee66c08c6c0d8c403efee00f73

Tx prefix hash: 310f1a644480c112a3bd27a84e225ca4946a5159fd3813ffcb9ad3d357fa08a3
Tx public key: ec4fef57490cd8d70656173a1d4c39ce3b8955fab75ed018b241af4a16e09eaa
Timestamp: 1761206145 Timestamp [UCT]: 2025-10-23 07:55:45 Age [y:d:h:m:s]: 00:035:21:59:38
Block: 1396061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25712 RingCT/type: yes/0
Extra: 01ec4fef57490cd8d70656173a1d4c39ce3b8955fab75ed018b241af4a16e09eaa021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8bcf613caf69a6a642881d7351a6fb66b06bc19179c1d1066f6fb83462eed18 0.600000000000 1884346 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": 1396071, "vin": [ { "gen": { "height": 1396061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8bcf613caf69a6a642881d7351a6fb66b06bc19179c1d1066f6fb83462eed18" } } ], "extra": [ 1, 236, 79, 239, 87, 73, 12, 216, 215, 6, 86, 23, 58, 29, 76, 57, 206, 59, 137, 85, 250, 183, 94, 208, 24, 178, 65, 175, 74, 22, 224, 158, 170, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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