Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c5d709a300f3954a20c72438d6cb3682f9ac26482ca4083e66d4b2ec951a6a

Tx prefix hash: a2174778aa5ec0385a96d9c7bb2622549c9d680d6f1a28dc76abe74f6eee5c13
Tx public key: e8860a2e5d36f8c7c9aa001e8f373a06ed382ebeaed8cb10ba9564bcc2b54c27
Timestamp: 1733425569 Timestamp [UCT]: 2024-12-05 19:06:09 Age [y:d:h:m:s]: 00:116:14:18:04
Block: 1168768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83109 RingCT/type: yes/0
Extra: 01e8860a2e5d36f8c7c9aa001e8f373a06ed382ebeaed8cb10ba9564bcc2b54c270211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b262e0c21f46c7c623baa2ef0fd8608676a58f24b003e8164bf2aaf4851eb40 0.600000000000 1654479 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": 1168778, "vin": [ { "gen": { "height": 1168768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b262e0c21f46c7c623baa2ef0fd8608676a58f24b003e8164bf2aaf4851eb40" } } ], "extra": [ 1, 232, 134, 10, 46, 93, 54, 248, 199, 201, 170, 0, 30, 143, 55, 58, 6, 237, 56, 46, 190, 174, 216, 203, 16, 186, 149, 100, 188, 194, 181, 76, 39, 2, 17, 0, 0, 0, 8, 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