Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac66c03a20902ea808c76e0ae6dd753321e390fb1efc90205435d99e27c434aa

Tx prefix hash: 9ca666cfe523af8cc3ff407396a44f6f49e7f4a2cc1aafdc2b1f4b7d3b4cc683
Tx public key: e2f6597ad8410153643979df7eef83dddb6e49e91b4312bcfb159d6f3bb49be8
Timestamp: 1716697332 Timestamp [UCT]: 2024-05-26 04:22:12 Age [y:d:h:m:s]: 00:189:05:04:45
Block: 1030180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135433 RingCT/type: yes/0
Extra: 01e2f6597ad8410153643979df7eef83dddb6e49e91b4312bcfb159d6f3bb49be802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97caf07db40772467e684896d4545e1d7cb77f8922e29a231605c269e3fcdec5 0.600000000000 1498433 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": 1030190, "vin": [ { "gen": { "height": 1030180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97caf07db40772467e684896d4545e1d7cb77f8922e29a231605c269e3fcdec5" } } ], "extra": [ 1, 226, 246, 89, 122, 216, 65, 1, 83, 100, 57, 121, 223, 126, 239, 131, 221, 219, 110, 73, 233, 27, 67, 18, 188, 251, 21, 157, 111, 59, 180, 155, 232, 2, 17, 0, 0, 0, 3, 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