Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c699c341be1f6f6313eba356daad350c8569999705dc482142c8407f489fa0

Tx prefix hash: 4e00c0b69ef3a8d824bc640c792e3a2e6e4432fd21b2773d18da47764b372f69
Tx public key: bf80a30082e2c24c7b47599a93c3a567119fad87cc91ee83d004833597d3b774
Timestamp: 1700404050 Timestamp [UCT]: 2023-11-19 14:27:30 Age [y:d:h:m:s]: 01:355:15:23:39
Block: 895100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513066 RingCT/type: yes/0
Extra: 01bf80a30082e2c24c7b47599a93c3a567119fad87cc91ee83d004833597d3b774021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.663990884000 dcy

stealth address amount amount idx
00: d3afc69194d441362c39d5c904c242b349a5749ed388c0587a614e18f56edef7 0.663990884000 1351323 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": 895110, "vin": [ { "gen": { "height": 895100 } } ], "vout": [ { "amount": 663990884, "target": { "key": "d3afc69194d441362c39d5c904c242b349a5749ed388c0587a614e18f56edef7" } } ], "extra": [ 1, 191, 128, 163, 0, 130, 226, 194, 76, 123, 71, 89, 154, 147, 195, 165, 103, 17, 159, 173, 135, 204, 145, 238, 131, 208, 4, 131, 53, 151, 211, 183, 116, 2, 17, 0, 0, 0, 4, 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