Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af9709eb5685c07709c066a6a8c8558e893b6bdac160c3021ba32cb26e7354f

Tx prefix hash: f8a67f4c0ad35302c01bdd56afb49a81862ac3a3191edc61aa1f45f5adc30ac2
Tx public key: 71f4556cfe0ae8fbe096c1a30e9f940c2de375b2a914600ecb0ba556852052ca
Timestamp: 1750598859 Timestamp [UCT]: 2025-06-22 13:27:39 Age [y:d:h:m:s]: 00:148:19:51:25
Block: 1310476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104238 RingCT/type: yes/0
Extra: 0171f4556cfe0ae8fbe096c1a30e9f940c2de375b2a914600ecb0ba556852052ca02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c123397c911e0c6f35689633a61a3874fed053dcd3597366c26f8c23d5a8765c 0.600000000000 1798097 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": 1310486, "vin": [ { "gen": { "height": 1310476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c123397c911e0c6f35689633a61a3874fed053dcd3597366c26f8c23d5a8765c" } } ], "extra": [ 1, 113, 244, 85, 108, 254, 10, 232, 251, 224, 150, 193, 163, 14, 159, 148, 12, 45, 227, 117, 178, 169, 20, 96, 14, 203, 11, 165, 86, 133, 32, 82, 202, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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