Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaeba6c9ee280ba8ce4fc2924f6aad67236d80ce4d975d5b054c3ead7b51e275

Tx prefix hash: 7faf600618576ef4553081a086237883e07f71397641e01fc37b67eafb642a71
Tx public key: 8d61bcad0393e8762cdabc4d2fc9f61097a3d92c61660cef7fbf9e980f45c53a
Timestamp: 1717634689 Timestamp [UCT]: 2024-06-06 00:44:49 Age [y:d:h:m:s]: 01:168:12:43:07
Block: 1037947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379025 RingCT/type: yes/0
Extra: 018d61bcad0393e8762cdabc4d2fc9f61097a3d92c61660cef7fbf9e980f45c53a021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd70cf7cd2280692ac48e5752e1c40a868f4aa0c2d8f63637194f612cb074a77 0.600000000000 1506506 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": 1037957, "vin": [ { "gen": { "height": 1037947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd70cf7cd2280692ac48e5752e1c40a868f4aa0c2d8f63637194f612cb074a77" } } ], "extra": [ 1, 141, 97, 188, 173, 3, 147, 232, 118, 44, 218, 188, 77, 47, 201, 246, 16, 151, 163, 217, 44, 97, 102, 12, 239, 127, 191, 158, 152, 15, 69, 197, 58, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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