Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ed5d741e2d9ea1440544cab0c56d40179d466adea72c63cfc11f61b40a28b32

Tx prefix hash: 7f59761da9a1fa5631350d3edd5c3e103c742cfca1ee38d2bf25f44021aafed5
Tx public key: 1828adc8d4d58627a5f6ec474500e9b553a087a68c8b1512abdedeca34782ca8
Timestamp: 1698330749 Timestamp [UCT]: 2023-10-26 14:32:29 Age [y:d:h:m:s]: 01:020:04:29:48
Block: 878127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275602 RingCT/type: yes/0
Extra: 011828adc8d4d58627a5f6ec474500e9b553a087a68c8b1512abdedeca34782ca80211000000044b8f5122000000000000000000

1 output(s) for total of 0.755789295000 dcy

stealth address amount amount idx
00: dcf6eae65abf5a7013b0d18963d079fad4849b4dfca8ee190217ffb8f1dc5269 0.755789295000 1333541 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": 878137, "vin": [ { "gen": { "height": 878127 } } ], "vout": [ { "amount": 755789295, "target": { "key": "dcf6eae65abf5a7013b0d18963d079fad4849b4dfca8ee190217ffb8f1dc5269" } } ], "extra": [ 1, 24, 40, 173, 200, 212, 213, 134, 39, 165, 246, 236, 71, 69, 0, 233, 181, 83, 160, 135, 166, 140, 139, 21, 18, 171, 222, 222, 202, 52, 120, 44, 168, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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