Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb646fb134ce07097172fbb41dd3a0e0f906c7f0922692a172faab5620f239e9

Tx prefix hash: 8cdf2dd823cccc0f4b890f471725833434472b11d3e886d1b2b35e4ea84671c8
Tx public key: da0b82f7cf8532e55ace93684a8130f1d948f0da52e518ce3127866ff381dfde
Timestamp: 1763058308 Timestamp [UCT]: 2025-11-13 18:25:08 Age [y:d:h:m:s]: 00:079:18:36:33
Block: 1411406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56936 RingCT/type: yes/0
Extra: 01da0b82f7cf8532e55ace93684a8130f1d948f0da52e518ce3127866ff381dfde021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5e868e4b1e68ab0ef89c3ba026b81725fbedf8684fa6b372ea8a9e6209fae5 0.600000000000 1899867 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": 1411416, "vin": [ { "gen": { "height": 1411406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5e868e4b1e68ab0ef89c3ba026b81725fbedf8684fa6b372ea8a9e6209fae5" } } ], "extra": [ 1, 218, 11, 130, 247, 207, 133, 50, 229, 90, 206, 147, 104, 74, 129, 48, 241, 217, 72, 240, 218, 82, 229, 24, 206, 49, 39, 134, 111, 243, 129, 223, 222, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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