Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ffa60d1846758c0b19ebfa3183d990d01bca58f905522c1ecce119868c5649

Tx prefix hash: cf7732fa59c15da668252ff2c89dd9c75c029259c9db1732f14f5a169c1f52a4
Tx public key: 13b974d9a7a2daa7c497fa9536350a98e84ee1ae02deb6012a8b18d35f64c6a1
Timestamp: 1748847183 Timestamp [UCT]: 2025-06-02 06:53:03 Age [y:d:h:m:s]: 00:172:07:16:38
Block: 1296171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120824 RingCT/type: yes/0
Extra: 0113b974d9a7a2daa7c497fa9536350a98e84ee1ae02deb6012a8b18d35f64c6a102110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa4ef2ae7ce18b383f9f950df3de6026261eb4d4813efb5f57d22afbc2b9554b 0.600000000000 1783678 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": 1296181, "vin": [ { "gen": { "height": 1296171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa4ef2ae7ce18b383f9f950df3de6026261eb4d4813efb5f57d22afbc2b9554b" } } ], "extra": [ 1, 19, 185, 116, 217, 167, 162, 218, 167, 196, 151, 250, 149, 54, 53, 10, 152, 232, 78, 225, 174, 2, 222, 182, 1, 42, 139, 24, 211, 95, 100, 198, 161, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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