Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7372c83e3fbe6ad8959b4a95b9508c9d4de166462ee95b7b1ccf1a7fab30839

Tx prefix hash: 27e33951ac06c630c8a3adbaa2af31f9b8f0a11ac4e78e7d1bebde26bf753459
Tx public key: c1da9039f34728414fdd801da9e98035d86e3ef0af6711f656350a1564b227fe
Timestamp: 1727699362 Timestamp [UCT]: 2024-09-30 12:29:22 Age [y:d:h:m:s]: 00:225:05:19:28
Block: 1121388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160801 RingCT/type: yes/0
Extra: 01c1da9039f34728414fdd801da9e98035d86e3ef0af6711f656350a1564b227fe021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6657bd1d836452e8f71b4ea5c77552dd25f7557a1fe1d08b4cb83bc0afa7221 0.600000000000 1603643 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": 1121398, "vin": [ { "gen": { "height": 1121388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6657bd1d836452e8f71b4ea5c77552dd25f7557a1fe1d08b4cb83bc0afa7221" } } ], "extra": [ 1, 193, 218, 144, 57, 243, 71, 40, 65, 79, 221, 128, 29, 169, 233, 128, 53, 216, 110, 62, 240, 175, 103, 17, 246, 86, 53, 10, 21, 100, 178, 39, 254, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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