Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c4b45b961b0fd9937a56dd572d322878a27c9f39739d114688b8b40b41a8737

Tx prefix hash: 5157ff8e07b7655b6765e53b04c4853d2bf0171eaee0de81e567e915d40f6829
Tx public key: 350be8c133d8dde22afbed995538007c227c1b2e262980d7ea20e6e3e66cc2fd
Timestamp: 1750550200 Timestamp [UCT]: 2025-06-21 23:56:40 Age [y:d:h:m:s]: 00:150:15:35:34
Block: 1310087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105522 RingCT/type: yes/0
Extra: 01350be8c133d8dde22afbed995538007c227c1b2e262980d7ea20e6e3e66cc2fd021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5792b798393723773e6724b5ad59953478f63d7dc7eb1305b3ff8b5a4dac9be2 0.600000000000 1797704 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": 1310097, "vin": [ { "gen": { "height": 1310087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5792b798393723773e6724b5ad59953478f63d7dc7eb1305b3ff8b5a4dac9be2" } } ], "extra": [ 1, 53, 11, 232, 193, 51, 216, 221, 226, 42, 251, 237, 153, 85, 56, 0, 124, 34, 124, 27, 46, 38, 41, 128, 215, 234, 32, 230, 227, 230, 108, 194, 253, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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