Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64802fb38d76912e9d9016d5004e3b816108440034df9dca54ccec848d3c8908

Tx prefix hash: 0a68f1e2aebf7db805752db5e09aa5da739cbbafe3859b4174cb84a26a07e654
Tx public key: 66c7d5db0778dc2a11e44c5703603e70e0952bb54ad6cc60b0c496ff5251414b
Timestamp: 1761252835 Timestamp [UCT]: 2025-10-23 20:53:55 Age [y:d:h:m:s]: 00:018:02:28:43
Block: 1396458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12945 RingCT/type: yes/0
Extra: 0166c7d5db0778dc2a11e44c5703603e70e0952bb54ad6cc60b0c496ff5251414b0211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a131677278dd78206a8f084a9a41c331b1cb9145ea25b8b69c4846d5402ede5f 0.600000000000 1884745 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": 1396468, "vin": [ { "gen": { "height": 1396458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a131677278dd78206a8f084a9a41c331b1cb9145ea25b8b69c4846d5402ede5f" } } ], "extra": [ 1, 102, 199, 213, 219, 7, 120, 220, 42, 17, 228, 76, 87, 3, 96, 62, 112, 224, 149, 43, 181, 74, 214, 204, 96, 176, 196, 150, 255, 82, 81, 65, 75, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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