Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaced97f65c05f2cbb90941a2af73a7a70224fc624a5b06ecdcca2f9fbf1c731

Tx prefix hash: fac734207581be5925807652a5623562eca38a2d5c6bd02b0bb0b7b20b143756
Tx public key: c6ae91845d90c88963ebd34e8807b554b5cfb4c4ef09a4f449fd9d5edec5a959
Timestamp: 1761337494 Timestamp [UCT]: 2025-10-24 20:24:54 Age [y:d:h:m:s]: 00:059:17:16:43
Block: 1397158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42730 RingCT/type: yes/0
Extra: 01c6ae91845d90c88963ebd34e8807b554b5cfb4c4ef09a4f449fd9d5edec5a959021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecf6ce7f13714ad901264e6eff4bef05bc5d748656397d88d8e59fecfa6a8aa7 0.600000000000 1885449 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": 1397168, "vin": [ { "gen": { "height": 1397158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecf6ce7f13714ad901264e6eff4bef05bc5d748656397d88d8e59fecfa6a8aa7" } } ], "extra": [ 1, 198, 174, 145, 132, 93, 144, 200, 137, 99, 235, 211, 78, 136, 7, 181, 84, 181, 207, 180, 196, 239, 9, 164, 244, 73, 253, 157, 94, 222, 197, 169, 89, 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