Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ab695f0f8b79ea29b69bc59fd8ac992f0053def19d80daf9e25751bdd9642a3

Tx prefix hash: a01a396b9cfd1f4feb8faf69bc51a142d331e8b447034e83825a102a4b779038
Tx public key: 0dd12348ec98e7c75fe3df178a731bb3f65a245d642c440381a3973bc1e29da7
Timestamp: 1712750315 Timestamp [UCT]: 2024-04-10 11:58:35 Age [y:d:h:m:s]: 01:066:13:33:17
Block: 997422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308495 RingCT/type: yes/0
Extra: 010dd12348ec98e7c75fe3df178a731bb3f65a245d642c440381a3973bc1e29da70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a43b794ca20e8efc8802d739f0331f3ac3046ec56d772e8971a68d42edb54b4 0.600000000000 1457854 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": 997432, "vin": [ { "gen": { "height": 997422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a43b794ca20e8efc8802d739f0331f3ac3046ec56d772e8971a68d42edb54b4" } } ], "extra": [ 1, 13, 209, 35, 72, 236, 152, 231, 199, 95, 227, 223, 23, 138, 115, 27, 179, 246, 90, 36, 93, 100, 44, 68, 3, 129, 163, 151, 59, 193, 226, 157, 167, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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