Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f70b698ebe51df58cf7fca86f28814c1750b8ed2e54437590af1f19762f8e81a

Tx prefix hash: 59d785d969569c1e2aae7433fbbc5498d53bdc75127a4c3ccea61f36649ece29
Tx public key: 9b2614e58471eae3a9cd790a5f7ff1005bd1e9f41947763c66dba9e1d5966ef5
Timestamp: 1759370246 Timestamp [UCT]: 2025-10-02 01:57:26 Age [y:d:h:m:s]: 00:098:16:59:19
Block: 1380830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70689 RingCT/type: yes/0
Extra: 019b2614e58471eae3a9cd790a5f7ff1005bd1e9f41947763c66dba9e1d5966ef5021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f161a2e8b411b9efbd92329ccf9879f9d3b114af0aece6a916d7f40993011fdd 0.600000000000 1868941 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": 1380840, "vin": [ { "gen": { "height": 1380830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f161a2e8b411b9efbd92329ccf9879f9d3b114af0aece6a916d7f40993011fdd" } } ], "extra": [ 1, 155, 38, 20, 229, 132, 113, 234, 227, 169, 205, 121, 10, 95, 127, 241, 0, 91, 209, 233, 244, 25, 71, 118, 60, 102, 219, 169, 225, 213, 150, 110, 245, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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