Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6969164eff153a57b9f5ff799e35bcc24d1b8322332975a20b5a32f417472d

Tx prefix hash: 051a1f45dcd6602754908252ac2bd40cf4f7173489609693c7784c455b2cdd55
Tx public key: df0f4a49d3a8e85165f06a4812a2b68688ab6302ea5c837ae5c20144110e65ac
Timestamp: 1708053952 Timestamp [UCT]: 2024-02-16 03:25:52 Age [y:d:h:m:s]: 01:050:08:58:23
Block: 958512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297031 RingCT/type: yes/0
Extra: 01df0f4a49d3a8e85165f06a4812a2b68688ab6302ea5c837ae5c20144110e65ac02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e64d2c467423d38e0bb5b8152e35b974dca4a4e261480528df00d70db219d1c 0.600000000000 1417871 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": 958522, "vin": [ { "gen": { "height": 958512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e64d2c467423d38e0bb5b8152e35b974dca4a4e261480528df00d70db219d1c" } } ], "extra": [ 1, 223, 15, 74, 73, 211, 168, 232, 81, 101, 240, 106, 72, 18, 162, 182, 134, 136, 171, 99, 2, 234, 92, 131, 122, 229, 194, 1, 68, 17, 14, 101, 172, 2, 17, 0, 0, 0, 6, 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