Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04ebf3cdf3f248589ae2b5920d7d1dd2b1e233a29d0d22d155d4e1d2be2ad184

Tx prefix hash: ef7fe98f7bd63f9e110bd723cdc2282851c1f2c741e6b79e71fb8d3b9782d80a
Tx public key: 21c08f04e79b131fd12208ffe87e6f13ec1b7cfda07638b97eee6f83647f886e
Timestamp: 1745530082 Timestamp [UCT]: 2025-04-24 21:28:02 Age [y:d:h:m:s]: 00:015:02:05:12
Block: 1268697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10793 RingCT/type: yes/0
Extra: 0121c08f04e79b131fd12208ffe87e6f13ec1b7cfda07638b97eee6f83647f886e021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923a11f698d8bb16bd8df50050e445ba1c15d531adea74f66fe70020bbefb8ed 0.600000000000 1755928 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": 1268707, "vin": [ { "gen": { "height": 1268697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923a11f698d8bb16bd8df50050e445ba1c15d531adea74f66fe70020bbefb8ed" } } ], "extra": [ 1, 33, 192, 143, 4, 231, 155, 19, 31, 209, 34, 8, 255, 232, 126, 111, 19, 236, 27, 124, 253, 160, 118, 56, 185, 126, 238, 111, 131, 100, 127, 136, 110, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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