Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c61dd38f4be529904d73625c88ef98549f9467073d95a6ab38f9bab44507194

Tx prefix hash: cdff587b50f9d85ecfb2f3d0490e9e4c3ff9b15c5b0f4f648f335a4ddad5b64e
Tx public key: 031196bbaf5a1ffc7781f4e1a503c369ccfd2bd1a85a0c8bab4e7d1e603ed14d
Timestamp: 1744712644 Timestamp [UCT]: 2025-04-15 10:24:04 Age [y:d:h:m:s]: 00:218:03:44:29
Block: 1261928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153643 RingCT/type: yes/0
Extra: 01031196bbaf5a1ffc7781f4e1a503c369ccfd2bd1a85a0c8bab4e7d1e603ed14d02110000000cdbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2dc923f656ae8f64bbee624c8950c60b3920d7aab47ce4151d55c4daf96a4e5 0.600000000000 1749103 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": 1261938, "vin": [ { "gen": { "height": 1261928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2dc923f656ae8f64bbee624c8950c60b3920d7aab47ce4151d55c4daf96a4e5" } } ], "extra": [ 1, 3, 17, 150, 187, 175, 90, 31, 252, 119, 129, 244, 225, 165, 3, 195, 105, 204, 253, 43, 209, 168, 90, 12, 139, 171, 78, 125, 30, 96, 62, 209, 77, 2, 17, 0, 0, 0, 12, 219, 181, 113, 193, 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