Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd05ba1122f4b2b1007efb703046de48a35d85915f07936111dd1e27a247b342

Tx prefix hash: e0c087f5e60c52a6d581a5a829d824e85825976a64d0ac948ba8961c37bf43a3
Tx public key: a32520e9884a095e11df379ff6d6e5db07ca62562f7ce9a883986254cb3ba4a4
Timestamp: 1765537015 Timestamp [UCT]: 2025-12-12 10:56:55 Age [y:d:h:m:s]: 00:026:01:17:09
Block: 1431946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18661 RingCT/type: yes/0
Extra: 01a32520e9884a095e11df379ff6d6e5db07ca62562f7ce9a883986254cb3ba4a402110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af768c1189a29c5f5d2f1aff68c493d760df2b8c9b8b1690e365695eb4ace543 0.600000000000 1920723 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": 1431956, "vin": [ { "gen": { "height": 1431946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af768c1189a29c5f5d2f1aff68c493d760df2b8c9b8b1690e365695eb4ace543" } } ], "extra": [ 1, 163, 37, 32, 233, 136, 74, 9, 94, 17, 223, 55, 159, 246, 214, 229, 219, 7, 202, 98, 86, 47, 124, 233, 168, 131, 152, 98, 84, 203, 59, 164, 164, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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