Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d44ab95aba77d346a19e0d6e5254c8fd306087055bc1b94b17a1af8c6b9c04c

Tx prefix hash: e7d4a459cd5994b15c4740600a2ea37a2abb8e86666d5c373a48a299954faee3
Tx public key: f5c7959a9c3c7e6617ceba81b44e7dc7028fadc347d4cb9472be2266c84ad61f
Timestamp: 1581748204 Timestamp [UCT]: 2020-02-15 06:30:04 Age [y:d:h:m:s]: 05:260:06:36:00
Block: 65501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336443 RingCT/type: yes/0
Extra: 01f5c7959a9c3c7e6617ceba81b44e7dc7028fadc347d4cb9472be2266c84ad61f02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 372.369349935000 dcy

stealth address amount amount idx
00: 54fd7941844eb72b84439069b9fa4c82ecc10e97858fd6adbb0f930f3a2fbd60 372.369349935000 120768 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": 65511, "vin": [ { "gen": { "height": 65501 } } ], "vout": [ { "amount": 372369349935, "target": { "key": "54fd7941844eb72b84439069b9fa4c82ecc10e97858fd6adbb0f930f3a2fbd60" } } ], "extra": [ 1, 245, 199, 149, 154, 156, 60, 126, 102, 23, 206, 186, 129, 180, 78, 125, 199, 2, 143, 173, 195, 71, 212, 203, 148, 114, 190, 34, 102, 200, 74, 214, 31, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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