Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc9c2cf6fd7943440587b230c29760d9346b68c4da8d64ff5df5e4b0863c7a19

Tx prefix hash: 1ae22e4878909db2c8a7fdb4f05ca1b71d81d941feefb49ba59728011faea5ee
Tx public key: a9a9c2396f89b73f8b18ab53512ade698e2189dfa07458cda6d326d66fd2b77c
Timestamp: 1710582034 Timestamp [UCT]: 2024-03-16 09:40:34 Age [y:d:h:m:s]: 01:060:12:12:32
Block: 979499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304231 RingCT/type: yes/0
Extra: 01a9a9c2396f89b73f8b18ab53512ade698e2189dfa07458cda6d326d66fd2b77c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d6ebc899d4e9c810ddca0f029cef73d32e2fc3b8695823f60233f9adb288af7 0.600000000000 1439532 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": 979509, "vin": [ { "gen": { "height": 979499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d6ebc899d4e9c810ddca0f029cef73d32e2fc3b8695823f60233f9adb288af7" } } ], "extra": [ 1, 169, 169, 194, 57, 111, 137, 183, 63, 139, 24, 171, 83, 81, 42, 222, 105, 142, 33, 137, 223, 160, 116, 88, 205, 166, 211, 38, 214, 111, 210, 183, 124, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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