Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf05baff171226966fc18b44ce2afa73e7596fec2c8a1c2d776a6586da6bd70

Tx prefix hash: 65dd1c33a83311def08096425135c427719f5968c0c5c7753ac2ef8485b69135
Tx public key: e0d6c1a5f72f6d0068e7707dcbca453906b91b5b0a6ed555adf21e5587d4ff3e
Timestamp: 1753856456 Timestamp [UCT]: 2025-07-30 06:20:56 Age [y:d:h:m:s]: 00:070:12:46:11
Block: 1336466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49178 RingCT/type: yes/0
Extra: 01e0d6c1a5f72f6d0068e7707dcbca453906b91b5b0a6ed555adf21e5587d4ff3e021100000002ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae0e3f511f60503cbe7e3507ba71fbbaade7876cacaed983d4ec902d9e45058 0.600000000000 1824267 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": 1336476, "vin": [ { "gen": { "height": 1336466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae0e3f511f60503cbe7e3507ba71fbbaade7876cacaed983d4ec902d9e45058" } } ], "extra": [ 1, 224, 214, 193, 165, 247, 47, 109, 0, 104, 231, 112, 125, 203, 202, 69, 57, 6, 185, 27, 91, 10, 110, 213, 85, 173, 242, 30, 85, 135, 212, 255, 62, 2, 17, 0, 0, 0, 2, 239, 34, 20, 133, 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