Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df190301c45fd1c804304409d49324966bcf66398f475c50d22fcd23fca5313a

Tx prefix hash: e2f13dc5c2601e916b475db61929589eeec8ebb352b9bbe83b21c3eeb70d748d
Tx public key: aac0d0ea6d2428a75d88b6857e493f8010f4e59ed75a27babab9d36246dbbde8
Timestamp: 1748471056 Timestamp [UCT]: 2025-05-28 22:24:16 Age [y:d:h:m:s]: 00:248:22:20:47
Block: 1293051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175530 RingCT/type: yes/0
Extra: 01aac0d0ea6d2428a75d88b6857e493f8010f4e59ed75a27babab9d36246dbbde8021100000001df096e52000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ee7337ed61b602c00fa8cea88e269e461d2b74508c96438d269f2c2a114103 0.600000000000 1780522 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": 1293061, "vin": [ { "gen": { "height": 1293051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ee7337ed61b602c00fa8cea88e269e461d2b74508c96438d269f2c2a114103" } } ], "extra": [ 1, 170, 192, 208, 234, 109, 36, 40, 167, 93, 136, 182, 133, 126, 73, 63, 128, 16, 244, 229, 158, 215, 90, 39, 186, 186, 185, 211, 98, 70, 219, 189, 232, 2, 17, 0, 0, 0, 1, 223, 9, 110, 82, 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