Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dfe54f458ac62da3b842c68c238efc8bb9818cf27a0e882f43d9255a18a71ca

Tx prefix hash: 76c799b1d2b7b0bbc5594cce11d5328d2dc3c303477619941dd3ecdbb3fc6f1c
Tx public key: 17f41a048f8aede8308ef16020483194e8910c5aa6e5280b9e61f7d27a00abdc
Timestamp: 1708523442 Timestamp [UCT]: 2024-02-21 13:50:42 Age [y:d:h:m:s]: 01:260:22:04:17
Block: 962407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445218 RingCT/type: yes/0
Extra: 0117f41a048f8aede8308ef16020483194e8910c5aa6e5280b9e61f7d27a00abdc0211000000140011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bf6a870f9757f63fac38d2d559fcaa34b3965346c22728bdc0bad275b74d807 0.600000000000 1422042 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": 962417, "vin": [ { "gen": { "height": 962407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bf6a870f9757f63fac38d2d559fcaa34b3965346c22728bdc0bad275b74d807" } } ], "extra": [ 1, 23, 244, 26, 4, 143, 138, 237, 232, 48, 142, 241, 96, 32, 72, 49, 148, 232, 145, 12, 90, 166, 229, 40, 11, 158, 97, 247, 210, 122, 0, 171, 220, 2, 17, 0, 0, 0, 20, 0, 17, 5, 91, 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