Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4d0946dc4719379a13e6c8ea5cd7957be9652a236160157665055733c67443

Tx prefix hash: 64d596925e79f58dca25350f4717d55e779b295a7834fe8e5407ddd788c13315
Tx public key: f4fa742f173b414d1c6bd99021be106161a2e572fa7e6c6d87364ca6d034de10
Timestamp: 1582330234 Timestamp [UCT]: 2020-02-22 00:10:34 Age [y:d:h:m:s]: 05:102:14:41:28
Block: 69754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1226653 RingCT/type: yes/0
Extra: 01f4fa742f173b414d1c6bd99021be106161a2e572fa7e6c6d87364ca6d034de100211000000104ac5aa02000000000000000000

1 output(s) for total of 360.476407122000 dcy

stealth address amount amount idx
00: 397e7ab9a252af8058e2db0cbc8e5553fd9139d728d44f6275f899ad6f4b15bf 360.476407122000 128752 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": 69764, "vin": [ { "gen": { "height": 69754 } } ], "vout": [ { "amount": 360476407122, "target": { "key": "397e7ab9a252af8058e2db0cbc8e5553fd9139d728d44f6275f899ad6f4b15bf" } } ], "extra": [ 1, 244, 250, 116, 47, 23, 59, 65, 77, 28, 107, 217, 144, 33, 190, 16, 97, 97, 162, 229, 114, 250, 126, 108, 109, 135, 54, 76, 166, 208, 52, 222, 16, 2, 17, 0, 0, 0, 16, 74, 197, 170, 2, 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