Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c6c02dd3170133349e341016195c20cbf97e097b1890f91979add132bc81f31

Tx prefix hash: 562dcbd56581ae89a7e6343d9c660314740f3c9d7467c083d6a4408b5530337d
Tx public key: 775ba963d05d91428f5c9ccd45c61f0cc93ae91d199c5db9537758acb5cfd8a3
Timestamp: 1711433775 Timestamp [UCT]: 2024-03-26 06:16:15 Age [y:d:h:m:s]: 01:084:04:48:36
Block: 986558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321056 RingCT/type: yes/0
Extra: 01775ba963d05d91428f5c9ccd45c61f0cc93ae91d199c5db9537758acb5cfd8a302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa005d6e66d3b4f012ea35512fbf397a42570ba8c8d6875e94c504b9749688b 0.600000000000 1446787 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": 986568, "vin": [ { "gen": { "height": 986558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa005d6e66d3b4f012ea35512fbf397a42570ba8c8d6875e94c504b9749688b" } } ], "extra": [ 1, 119, 91, 169, 99, 208, 93, 145, 66, 143, 92, 156, 205, 69, 198, 31, 12, 201, 58, 233, 29, 25, 156, 93, 185, 83, 119, 88, 172, 181, 207, 216, 163, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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