Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccd8e28ab49812e79bad9a7ca1f9fe5fd2439de5a3fc619163a1f6e124baf85a

Tx prefix hash: ad8c22b0c94762fd872048ea9b0c35253d4f82259db796d4657cb2e0b153e2a3
Tx public key: 3769f6c80a55bfac18620f08889abd99f88a690644e99bf46bf711a4b48b53b2
Timestamp: 1752209313 Timestamp [UCT]: 2025-07-11 04:48:33 Age [y:d:h:m:s]: 00:179:16:57:23
Block: 1323048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127123 RingCT/type: yes/0
Extra: 013769f6c80a55bfac18620f08889abd99f88a690644e99bf46bf711a4b48b53b2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44e8c955d38df0eb8d0450317f5eae457da33d153141a229eb834c6f015661cf 0.600000000000 1810783 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": 1323058, "vin": [ { "gen": { "height": 1323048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44e8c955d38df0eb8d0450317f5eae457da33d153141a229eb834c6f015661cf" } } ], "extra": [ 1, 55, 105, 246, 200, 10, 85, 191, 172, 24, 98, 15, 8, 136, 154, 189, 153, 248, 138, 105, 6, 68, 233, 155, 244, 107, 247, 17, 164, 180, 139, 83, 178, 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