Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d64012be74c12b59818b49bb4154eb1d645e2dc9ba192abf68c5e05055e3fd56

Tx prefix hash: 2ce0ee588689b1b4278c1ba9a44b8a51000fb3dc64572f9691938ae9a21c0f50
Tx public key: c862850279830c524d8fa5c636b77bdd4e927f90f39de13eced277c810b48856
Timestamp: 1744916777 Timestamp [UCT]: 2025-04-17 19:06:17 Age [y:d:h:m:s]: 00:028:09:45:40
Block: 1263606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20327 RingCT/type: yes/0
Extra: 01c862850279830c524d8fa5c636b77bdd4e927f90f39de13eced277c810b48856021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 738e98f09b9ba866dc733c6b68a7ebf3e62f85faf2ecde79b1ea9517caa40f64 0.600000000000 1750797 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": 1263616, "vin": [ { "gen": { "height": 1263606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "738e98f09b9ba866dc733c6b68a7ebf3e62f85faf2ecde79b1ea9517caa40f64" } } ], "extra": [ 1, 200, 98, 133, 2, 121, 131, 12, 82, 77, 143, 165, 198, 54, 183, 123, 221, 78, 146, 127, 144, 243, 157, 225, 62, 206, 210, 119, 200, 16, 180, 136, 86, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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