Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cf3ccbd6ffd1b3e020d0129733d47b2033c49f485f1f6755bb71d3e4b32ece3

Tx prefix hash: 94dfdf4108035811c20ddd22ee02e46292070c6604136e649d0934d0c432687a
Tx public key: 3d23ab3d98cd92e57b8c6329489dc9aba53e1b254656c4d9287fda314b0ec198
Timestamp: 1713509861 Timestamp [UCT]: 2024-04-19 06:57:41 Age [y:d:h:m:s]: 01:019:01:29:05
Block: 1003747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274578 RingCT/type: yes/0
Extra: 013d23ab3d98cd92e57b8c6329489dc9aba53e1b254656c4d9287fda314b0ec198021100000006e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f796ee70f7e8841fd5bbaa0dc9f2178908f889d0f0eb55b25998294f2ef832c 0.600000000000 1464289 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": 1003757, "vin": [ { "gen": { "height": 1003747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f796ee70f7e8841fd5bbaa0dc9f2178908f889d0f0eb55b25998294f2ef832c" } } ], "extra": [ 1, 61, 35, 171, 61, 152, 205, 146, 229, 123, 140, 99, 41, 72, 157, 201, 171, 165, 62, 27, 37, 70, 86, 196, 217, 40, 127, 218, 49, 75, 14, 193, 152, 2, 17, 0, 0, 0, 6, 228, 187, 107, 131, 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