Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98494439025142cea6a4cd4a1425a78a4601f8656c1afce46c7eb3c24eff9c0d

Tx prefix hash: f4c219ff7520ec56500dbf92c57db30e7de53be0ca94fcda750584024c847e9a
Tx public key: d3ea94656523cf842e776e0a2fd5287efe0f76df1b57ab0c0b3365252b9ad0b5
Timestamp: 1761855345 Timestamp [UCT]: 2025-10-30 20:15:45 Age [y:d:h:m:s]: 00:069:23:35:24
Block: 1401451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50104 RingCT/type: yes/0
Extra: 01d3ea94656523cf842e776e0a2fd5287efe0f76df1b57ab0c0b3365252b9ad0b5021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae1893ae2fb32deefc03f0728d5e0c1b9c1bac38de0d567829214e6f7c011436 0.600000000000 1889770 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": 1401461, "vin": [ { "gen": { "height": 1401451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae1893ae2fb32deefc03f0728d5e0c1b9c1bac38de0d567829214e6f7c011436" } } ], "extra": [ 1, 211, 234, 148, 101, 101, 35, 207, 132, 46, 119, 110, 10, 47, 213, 40, 126, 254, 15, 118, 223, 27, 87, 171, 12, 11, 51, 101, 37, 43, 154, 208, 181, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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