Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffde7ad806108a37ae89997234a50622ffda3dc98309ef025d669a2273632d41

Tx prefix hash: c9c4e2199e76814fe4b3b49cd3eb0d53df2e662712f90536528c7c9ca0da285f
Tx public key: 734c63f8840bc0b4c4933242225518d1be98f8f4f64e0c8b13c2550bcad09a83
Timestamp: 1582035524 Timestamp [UCT]: 2020-02-18 14:18:44 Age [y:d:h:m:s]: 05:267:03:27:19
Block: 67500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1341733 RingCT/type: yes/0
Extra: 01734c63f8840bc0b4c4933242225518d1be98f8f4f64e0c8b13c2550bcad09a8302110000000112c4732d000000000000000000

1 output(s) for total of 366.729027472000 dcy

stealth address amount amount idx
00: e412edb9cc6559cbe1353904dddbff10aaf9a12c9f50e5f664571e27b47bdb2e 366.729027472000 124359 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": 67510, "vin": [ { "gen": { "height": 67500 } } ], "vout": [ { "amount": 366729027472, "target": { "key": "e412edb9cc6559cbe1353904dddbff10aaf9a12c9f50e5f664571e27b47bdb2e" } } ], "extra": [ 1, 115, 76, 99, 248, 132, 11, 192, 180, 196, 147, 50, 66, 34, 85, 24, 209, 190, 152, 248, 244, 246, 78, 12, 139, 19, 194, 85, 11, 202, 208, 154, 131, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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