Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf2f3cd8ad21636864e9a0091ccc59bffa637beaeb4a323efb8348162e2561a2

Tx prefix hash: e77474ce756b5c1a0317da9dbe394a35b4fa1846f5213d4eca648ddd164de20c
Tx public key: d3a6a234fc4f7557e0d9b31a38dba31f5854ebe63266d8b259a143ec3492a3b8
Timestamp: 1712444716 Timestamp [UCT]: 2024-04-06 23:05:16 Age [y:d:h:m:s]: 01:207:18:04:26
Block: 994886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407184 RingCT/type: yes/0
Extra: 01d3a6a234fc4f7557e0d9b31a38dba31f5854ebe63266d8b259a143ec3492a3b80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd74af81baf5a94423a7161dff67cf6bfc7eaf6b0e83469b937a8c62e1eb89dd 0.600000000000 1455290 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": 994896, "vin": [ { "gen": { "height": 994886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd74af81baf5a94423a7161dff67cf6bfc7eaf6b0e83469b937a8c62e1eb89dd" } } ], "extra": [ 1, 211, 166, 162, 52, 252, 79, 117, 87, 224, 217, 179, 26, 56, 219, 163, 31, 88, 84, 235, 230, 50, 102, 216, 178, 89, 161, 67, 236, 52, 146, 163, 184, 2, 17, 0, 0, 0, 1, 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