Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69192e0d88d4406971458d67a64b3679e34df0fe3aafa6a46ed6c62ba3cf3a93

Tx prefix hash: f807a099e4df42589f62c85a53d4b8bed23e96db877e591c40e1a6febe4b46b6
Tx public key: 38b59c454b326cc7078d92006dfaca821c7ae0b0e374e9ceabf65c6693c7e3b3
Timestamp: 1765537306 Timestamp [UCT]: 2025-12-12 11:01:46 Age [y:d:h:m:s]: 00:050:07:49:31
Block: 1431947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35849 RingCT/type: yes/0
Extra: 0138b59c454b326cc7078d92006dfaca821c7ae0b0e374e9ceabf65c6693c7e3b302110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93584eee9d93cbfc28f40c5cc6279665787e69a1cbc5e6422042f52325738a50 0.600000000000 1920724 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": 1431957, "vin": [ { "gen": { "height": 1431947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93584eee9d93cbfc28f40c5cc6279665787e69a1cbc5e6422042f52325738a50" } } ], "extra": [ 1, 56, 181, 156, 69, 75, 50, 108, 199, 7, 141, 146, 0, 109, 250, 202, 130, 28, 122, 224, 176, 227, 116, 233, 206, 171, 246, 92, 102, 147, 199, 227, 179, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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