Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2080d65a8fcbca3feb9b25cf01c3345bc0553aabf2d4b9a929b80b1b0837008

Tx prefix hash: dc85d3d3316d35ab6f84f916baef919504cef50bcab42c8fcea621d368d26c24
Tx public key: d433e48dfa461e12243165b55ec459f8a1881e33be8f6d283c24c7cef7e4ec6a
Timestamp: 1750692775 Timestamp [UCT]: 2025-06-23 15:32:55 Age [y:d:h:m:s]: 00:199:12:29:17
Block: 1311213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140581 RingCT/type: yes/0
Extra: 01d433e48dfa461e12243165b55ec459f8a1881e33be8f6d283c24c7cef7e4ec6a021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3b3f54b691ee6276d8a6d80da911f895949a110b6b53c14963f9e859c145cc2 0.600000000000 1798838 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": 1311223, "vin": [ { "gen": { "height": 1311213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3b3f54b691ee6276d8a6d80da911f895949a110b6b53c14963f9e859c145cc2" } } ], "extra": [ 1, 212, 51, 228, 141, 250, 70, 30, 18, 36, 49, 101, 181, 94, 196, 89, 248, 161, 136, 30, 51, 190, 143, 109, 40, 60, 36, 199, 206, 247, 228, 236, 106, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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