Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1235f85697c6a038d21016342ccb36269daf89ece9e3859c7b31a52c61386956

Tx prefix hash: f898bdedb9fbcf499289074c20f2388fa4a1e793350212449484b2ebd72933b1
Tx public key: f5096b6cd4eb53a90815e68331c971f20d35f6f6b1c9d9e432967119d6596b36
Timestamp: 1721967207 Timestamp [UCT]: 2024-07-26 04:13:27 Age [y:d:h:m:s]: 00:255:00:28:05
Block: 1073858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182166 RingCT/type: yes/0
Extra: 01f5096b6cd4eb53a90815e68331c971f20d35f6f6b1c9d9e432967119d6596b36021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e7b7ea9f5c0636709fb68e2b248b27310af1d19589b372c331465d0a25b250a 0.600000000000 1546365 of 15

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": 1073868, "vin": [ { "gen": { "height": 1073858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e7b7ea9f5c0636709fb68e2b248b27310af1d19589b372c331465d0a25b250a" } } ], "extra": [ 1, 245, 9, 107, 108, 212, 235, 83, 169, 8, 21, 230, 131, 49, 201, 113, 242, 13, 53, 246, 246, 177, 201, 217, 228, 50, 150, 113, 25, 214, 89, 107, 54, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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