Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856860aa763695ad8c1bf02344920d8a3b637fc2882a2bc8cc922d785510e455

Tx prefix hash: 1f91370215a51ae07556078f2d968d5d0b5113369d22c318f9d51a275db11d51
Tx public key: 82111f100074a815a561d597143c41d7d1a9eabbbeeff27bc70dc3e5b82ff40b
Timestamp: 1745298660 Timestamp [UCT]: 2025-04-22 05:11:00 Age [y:d:h:m:s]: 00:022:12:34:50
Block: 1266774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16133 RingCT/type: yes/0
Extra: 0182111f100074a815a561d597143c41d7d1a9eabbbeeff27bc70dc3e5b82ff40b021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cafdcb48bcc0cbcf707da23d3f2835bdd0cc3d90e7aefc8aaddf44d26b3a1a55 0.600000000000 1753995 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": 1266784, "vin": [ { "gen": { "height": 1266774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cafdcb48bcc0cbcf707da23d3f2835bdd0cc3d90e7aefc8aaddf44d26b3a1a55" } } ], "extra": [ 1, 130, 17, 31, 16, 0, 116, 168, 21, 165, 97, 213, 151, 20, 60, 65, 215, 209, 169, 234, 187, 190, 239, 242, 123, 199, 13, 195, 229, 184, 47, 244, 11, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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