Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e838fb4ad8f76b2612c307aa52df1213a725730f951bb160d561b28aa92d6dd

Tx prefix hash: 0435ff7e30539656d0a1484ef76c944bf92b3e3baf1edc55a979451ee13f63f0
Tx public key: a8df764b6f64400aeb2ed716a8354a2105abcae74183e1107a69e32ebc8ad367
Timestamp: 1759398638 Timestamp [UCT]: 2025-10-02 09:50:38 Age [y:d:h:m:s]: 00:095:14:30:15
Block: 1381067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68482 RingCT/type: yes/0
Extra: 01a8df764b6f64400aeb2ed716a8354a2105abcae74183e1107a69e32ebc8ad36702110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc83578baecdf528949a8b311a655627cd2f7d2fd485c09c5a8fbc79c9cf9995 0.600000000000 1869182 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": 1381077, "vin": [ { "gen": { "height": 1381067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc83578baecdf528949a8b311a655627cd2f7d2fd485c09c5a8fbc79c9cf9995" } } ], "extra": [ 1, 168, 223, 118, 75, 111, 100, 64, 10, 235, 46, 215, 22, 168, 53, 74, 33, 5, 171, 202, 231, 65, 131, 225, 16, 122, 105, 227, 46, 188, 138, 211, 103, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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