Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c68be52b0777a40281242cfb335665e44810b64b3f7cc470e8cb9cc23519cbb

Tx prefix hash: a6b65878c5cb21e01081a66bf3666fbe724e28a93f769189fe32a2f2c80ab56c
Tx public key: 1bc5c8bdffe7aa4bea0f1532340f54031d7cc1381a79bbdd03788970ef3c72f4
Timestamp: 1761866356 Timestamp [UCT]: 2025-10-30 23:19:16 Age [y:d:h:m:s]: 00:010:04:52:57
Block: 1401542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7292 RingCT/type: yes/0
Extra: 011bc5c8bdffe7aa4bea0f1532340f54031d7cc1381a79bbdd03788970ef3c72f4021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6b9e1f1ead52ac4baa8a91d8f44a78d834cb66187bd8692e866a1233369a9a6 0.600000000000 1889861 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": 1401552, "vin": [ { "gen": { "height": 1401542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6b9e1f1ead52ac4baa8a91d8f44a78d834cb66187bd8692e866a1233369a9a6" } } ], "extra": [ 1, 27, 197, 200, 189, 255, 231, 170, 75, 234, 15, 21, 50, 52, 15, 84, 3, 29, 124, 193, 56, 26, 121, 187, 221, 3, 120, 137, 112, 239, 60, 114, 244, 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