Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 075691506f7ed40a79a421f0ced1aada1e2b47b98d3b72bd6830bf54b2138cdd

Tx prefix hash: a17619e98e41c656c736031ac6c0e1dcd2ff8392bdeb88de3fb5f046b266de43
Tx public key: d7c380753e3c17cde58b5f73f005019c18d3115454e492e8330abce57ceb8b15
Timestamp: 1712520691 Timestamp [UCT]: 2024-04-07 20:11:31 Age [y:d:h:m:s]: 00:343:14:53:06
Block: 995514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245716 RingCT/type: yes/0
Extra: 01d7c380753e3c17cde58b5f73f005019c18d3115454e492e8330abce57ceb8b150211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e450b80e1f0676fb207e56f9710eb4de311a89593c3b7beac66e5c28b66c444c 0.600000000000 1455924 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": 995524, "vin": [ { "gen": { "height": 995514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e450b80e1f0676fb207e56f9710eb4de311a89593c3b7beac66e5c28b66c444c" } } ], "extra": [ 1, 215, 195, 128, 117, 62, 60, 23, 205, 229, 139, 95, 115, 240, 5, 1, 156, 24, 211, 17, 84, 84, 228, 146, 232, 51, 10, 188, 229, 124, 235, 139, 21, 2, 17, 0, 0, 0, 2, 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