Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 568b481ea3c4bfecfde740c529abd7972053bc8a9aae784ee259bd2a5e01a8d0

Tx prefix hash: cc060ab6bdc522e67be502fec5e67787a4e50748605e3549373f88c7169e6d1d
Tx public key: 4565cacf82775a6c8dd4e9b1fc50b16237b564afe60080cccbb17b8cdb2dc7a6
Timestamp: 1764426938 Timestamp [UCT]: 2025-11-29 14:35:38 Age [y:d:h:m:s]: 00:023:21:51:29
Block: 1422755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17102 RingCT/type: yes/0
Extra: 014565cacf82775a6c8dd4e9b1fc50b16237b564afe60080cccbb17b8cdb2dc7a6021100000003da554848000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 299443ad3569e13a6959876e0ebe3f9f01c711536c0d3f67b64fd479d096f0b3 0.600000000000 1911328 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": 1422765, "vin": [ { "gen": { "height": 1422755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "299443ad3569e13a6959876e0ebe3f9f01c711536c0d3f67b64fd479d096f0b3" } } ], "extra": [ 1, 69, 101, 202, 207, 130, 119, 90, 108, 141, 212, 233, 177, 252, 80, 177, 98, 55, 181, 100, 175, 230, 0, 128, 204, 203, 177, 123, 140, 219, 45, 199, 166, 2, 17, 0, 0, 0, 3, 218, 85, 72, 72, 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