Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca2105dea614ff0d1bce1b14d76b358dfae1db23a8e89a008ec43a06bf1a6b14

Tx prefix hash: 16152b52e350e9a8437d2da332ecbcd768f54595fde46c59ca964f6b8b32e29a
Tx public key: 4166728e7d596692cb4bc122a4f0ffd72dc7fc76af96cd8435b614375ff74376
Timestamp: 1765109903 Timestamp [UCT]: 2025-12-07 12:18:23 Age [y:d:h:m:s]: 00:023:03:36:42
Block: 1428405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16577 RingCT/type: yes/0
Extra: 014166728e7d596692cb4bc122a4f0ffd72dc7fc76af96cd8435b614375ff7437602110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad4c88ea2c3774fe246a1eb8767a12f2debc0fd1ada58f6bea6b4044b5a473b 0.600000000000 1917122 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": 1428415, "vin": [ { "gen": { "height": 1428405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad4c88ea2c3774fe246a1eb8767a12f2debc0fd1ada58f6bea6b4044b5a473b" } } ], "extra": [ 1, 65, 102, 114, 142, 125, 89, 102, 146, 203, 75, 193, 34, 164, 240, 255, 215, 45, 199, 252, 118, 175, 150, 205, 132, 53, 182, 20, 55, 95, 247, 67, 118, 2, 17, 0, 0, 0, 13, 214, 225, 157, 124, 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