Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50597bb96d3515047e810d577a24f05701ba6aeee6d000d9b176365ebd35302

Tx prefix hash: 842b88d3f3fc6fee42502c533f98aebea5d4bbd72a7fe32b7d46f99d469242ee
Tx public key: 4c9e7373898d20d8fe448a4b7f1b74e51bb1887a90e2809f261020afe92b06b0
Timestamp: 1762848306 Timestamp [UCT]: 2025-11-11 08:05:06 Age [y:d:h:m:s]: 00:042:16:01:23
Block: 1409660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30540 RingCT/type: yes/0
Extra: 014c9e7373898d20d8fe448a4b7f1b74e51bb1887a90e2809f261020afe92b06b0021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89d37a3b9c4a8e0bbbcb026957da094a2fcc8a3d720a9dab506c73901158dc33 0.600000000000 1898107 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": 1409670, "vin": [ { "gen": { "height": 1409660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89d37a3b9c4a8e0bbbcb026957da094a2fcc8a3d720a9dab506c73901158dc33" } } ], "extra": [ 1, 76, 158, 115, 115, 137, 141, 32, 216, 254, 68, 138, 75, 127, 27, 116, 229, 27, 177, 136, 122, 144, 226, 128, 159, 38, 16, 32, 175, 233, 43, 6, 176, 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