Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9390cade60d1f3b6e851d40e7734000718def36c1884bd182cefbcc19e2fb6f5

Tx prefix hash: 6658b3bab28727d62c1d53ac06c9e23daeeb8cad5bb3a8f277d9d075df807286
Tx public key: ffc96646dfee3303133542216de38d26e74df923d3228f6a48cd9c4d46e8ead2
Timestamp: 1753575364 Timestamp [UCT]: 2025-07-27 00:16:04 Age [y:d:h:m:s]: 00:084:05:33:08
Block: 1334136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59006 RingCT/type: yes/0
Extra: 01ffc96646dfee3303133542216de38d26e74df923d3228f6a48cd9c4d46e8ead2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 659b33f16942b93774cfb435d7cc223ad4e97f8fa49accb6ffc53ec06903e6f8 0.600000000000 1821937 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": 1334146, "vin": [ { "gen": { "height": 1334136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "659b33f16942b93774cfb435d7cc223ad4e97f8fa49accb6ffc53ec06903e6f8" } } ], "extra": [ 1, 255, 201, 102, 70, 223, 238, 51, 3, 19, 53, 66, 33, 109, 227, 141, 38, 231, 77, 249, 35, 211, 34, 143, 106, 72, 205, 156, 77, 70, 232, 234, 210, 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