Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d605e0dbc9b3858f0e421030b5b9ba8cb267b486d329e9e34a30ccb6c0c7d811

Tx prefix hash: c23ec42b1303688fff890cfa702a644d14cfc6a39c80f94bb6259fbf7c03cb19
Tx public key: 728875301ea9bc6839af8221255f81bc8473d858f12dd9a3a9408331f511f67d
Timestamp: 1749253780 Timestamp [UCT]: 2025-06-06 23:49:40 Age [y:d:h:m:s]: 00:156:18:04:50
Block: 1299524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109712 RingCT/type: yes/0
Extra: 01728875301ea9bc6839af8221255f81bc8473d858f12dd9a3a9408331f511f67d021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c79f6abded8da275fc3fd16bfc71980adc5c18286f25b031e5fbd74e1db5cb02 0.600000000000 1787061 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": 1299534, "vin": [ { "gen": { "height": 1299524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c79f6abded8da275fc3fd16bfc71980adc5c18286f25b031e5fbd74e1db5cb02" } } ], "extra": [ 1, 114, 136, 117, 48, 30, 169, 188, 104, 57, 175, 130, 33, 37, 95, 129, 188, 132, 115, 216, 88, 241, 45, 217, 163, 169, 64, 131, 49, 245, 17, 246, 125, 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