Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6aadfa3f3ea0314e0ef78e28b2e306aea80c2cc955a15efd30a691aade808937

Tx prefix hash: b9e0e9456fc6e8263b828efde76ab6f9f037f730360511289670ad633f2611af
Tx public key: 753bb6235cbf0859f81033cb8a8340e1d3b389e94d6eed3b1b9253b17cb9ddaa
Timestamp: 1705395685 Timestamp [UCT]: 2024-01-16 09:01:25 Age [y:d:h:m:s]: 01:295:23:17:04
Block: 936460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470348 RingCT/type: yes/0
Extra: 01753bb6235cbf0859f81033cb8a8340e1d3b389e94d6eed3b1b9253b17cb9ddaa0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600080000000 dcy

stealth address amount amount idx
00: 8c602e424e6765716d232974f69fd76063ea87a9524989208ad072e72ce2770d 0.600080000000 1394486 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": 936470, "vin": [ { "gen": { "height": 936460 } } ], "vout": [ { "amount": 600080000, "target": { "key": "8c602e424e6765716d232974f69fd76063ea87a9524989208ad072e72ce2770d" } } ], "extra": [ 1, 117, 59, 182, 35, 92, 191, 8, 89, 248, 16, 51, 203, 138, 131, 64, 225, 211, 179, 137, 233, 77, 110, 237, 59, 27, 146, 83, 177, 124, 185, 221, 170, 2, 17, 0, 0, 0, 8, 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