Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03da92eb29d4cde91140560ca350cc8700dbd8bc864c0d76eb40d3b595b17026

Tx prefix hash: 1f912703cac205b4403a5573d7880b098d98a684feb2608a74aa513f6ab930cd
Tx public key: 64d3f3c80f2a4fef65f856d22a9cb392a9389b284edd59109f619c2b7e825416
Timestamp: 1732853652 Timestamp [UCT]: 2024-11-29 04:14:12 Age [y:d:h:m:s]: 00:132:23:22:42
Block: 1164017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94852 RingCT/type: yes/0
Extra: 0164d3f3c80f2a4fef65f856d22a9cb392a9389b284edd59109f619c2b7e8254160211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8810800aae276254c031ed52f5313ec69f1ccdefc9dea171a238f7ef47d91b15 0.600000000000 1649688 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": 1164027, "vin": [ { "gen": { "height": 1164017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8810800aae276254c031ed52f5313ec69f1ccdefc9dea171a238f7ef47d91b15" } } ], "extra": [ 1, 100, 211, 243, 200, 15, 42, 79, 239, 101, 248, 86, 210, 42, 156, 179, 146, 169, 56, 155, 40, 78, 221, 89, 16, 159, 97, 156, 43, 126, 130, 84, 22, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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