Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c9c61c0683299170ca0835ae560312a416b6dbd17373176d17741ae97c53a4

Tx prefix hash: b525f05525b451f773b49989c89eb1f09a786a1935179a6a337c058829755ea9
Tx public key: 332a8e5b3f027a8b2f6891aa12ccf82c9c35e8a8c4d3b34167469f0153f47bec
Timestamp: 1714398458 Timestamp [UCT]: 2024-04-29 13:47:38 Age [y:d:h:m:s]: 00:304:15:08:22
Block: 1011115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217740 RingCT/type: yes/0
Extra: 01332a8e5b3f027a8b2f6891aa12ccf82c9c35e8a8c4d3b34167469f0153f47bec02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 112e9e93564ac2938ffb010bb945034a9b3e17753c50f5142d864ff398af84b5 0.600000000000 1473255 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": 1011125, "vin": [ { "gen": { "height": 1011115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "112e9e93564ac2938ffb010bb945034a9b3e17753c50f5142d864ff398af84b5" } } ], "extra": [ 1, 51, 42, 142, 91, 63, 2, 122, 139, 47, 104, 145, 170, 18, 204, 248, 44, 156, 53, 232, 168, 196, 211, 179, 65, 103, 70, 159, 1, 83, 244, 123, 236, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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