Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcb8c198f3ac44331ea7af98d4c21e5b6dd56b592dfcdf7a245b1e63c6bdac96

Tx prefix hash: 468363c49a39bd9a631d90e0714a547c7368d9bba763b4eb7845a3da8de1f062
Tx public key: c644cca77cc1f35e3fc36a215266ffbde665db9087baf141222819142668ee0f
Timestamp: 1695498098 Timestamp [UCT]: 2023-09-23 19:41:38 Age [y:d:h:m:s]: 01:194:14:06:09
Block: 854618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400142 RingCT/type: yes/0
Extra: 01c644cca77cc1f35e3fc36a215266ffbde665db9087baf141222819142668ee0f021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.904265261000 dcy

stealth address amount amount idx
00: 4adcff1006f0a6843a040e0ef7f4f7faedf7e02664d37b3dc877c4e41aa225b7 0.904265261000 1308602 of 0

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": 854628, "vin": [ { "gen": { "height": 854618 } } ], "vout": [ { "amount": 904265261, "target": { "key": "4adcff1006f0a6843a040e0ef7f4f7faedf7e02664d37b3dc877c4e41aa225b7" } } ], "extra": [ 1, 198, 68, 204, 167, 124, 193, 243, 94, 63, 195, 106, 33, 82, 102, 255, 189, 230, 101, 219, 144, 135, 186, 241, 65, 34, 40, 25, 20, 38, 104, 238, 15, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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