Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d241327bfa046cfdb27ee773a278ba19f8573d4a313adfcf412a36d0439b3b8e

Tx prefix hash: 05cef238a945e35a34023cdd247e4820f54b11a9aa2fa935362de0ea552362f1
Tx public key: aae8df0275f01233da202e938f8b35d68a52faf3186bc0caa99e27bd360b049f
Timestamp: 1760146222 Timestamp [UCT]: 2025-10-11 01:30:22 Age [y:d:h:m:s]: 00:086:20:36:26
Block: 1387264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62218 RingCT/type: yes/0
Extra: 01aae8df0275f01233da202e938f8b35d68a52faf3186bc0caa99e27bd360b049f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dded86e193ff95a9c0ac795bb2c537b925bb4cf649231a202ed5b3e7bf13746 0.600000000000 1875451 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": 1387274, "vin": [ { "gen": { "height": 1387264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dded86e193ff95a9c0ac795bb2c537b925bb4cf649231a202ed5b3e7bf13746" } } ], "extra": [ 1, 170, 232, 223, 2, 117, 240, 18, 51, 218, 32, 46, 147, 143, 139, 53, 214, 138, 82, 250, 243, 24, 107, 192, 202, 169, 158, 39, 189, 54, 11, 4, 159, 2, 17, 0, 0, 0, 1, 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