Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3cebb50246ebae5c53f932c5d33720d5f33e67cded22eb447facd781185cb52

Tx prefix hash: 1e768dd97ac5e24e29318578808c2971d8a87294de15b14da4754b17316a3822
Tx public key: cc526ff59f047111c31fceeb69d652dbef22edc2d4af3e0913c9d75c939c4fa9
Timestamp: 1695386378 Timestamp [UCT]: 2023-09-22 12:39:38 Age [y:d:h:m:s]: 01:182:18:14:34
Block: 853695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391682 RingCT/type: yes/0
Extra: 01cc526ff59f047111c31fceeb69d652dbef22edc2d4af3e0913c9d75c939c4fa90211000000064b8f5122000000000000000000

1 output(s) for total of 0.910655533000 dcy

stealth address amount amount idx
00: ea9a8d89d9eabeedf9cbe68f011e72ce967a8b6aa84797179fe0dadbfd24815d 0.910655533000 1307625 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": 853705, "vin": [ { "gen": { "height": 853695 } } ], "vout": [ { "amount": 910655533, "target": { "key": "ea9a8d89d9eabeedf9cbe68f011e72ce967a8b6aa84797179fe0dadbfd24815d" } } ], "extra": [ 1, 204, 82, 111, 245, 159, 4, 113, 17, 195, 31, 206, 235, 105, 214, 82, 219, 239, 34, 237, 194, 212, 175, 62, 9, 19, 201, 215, 92, 147, 156, 79, 169, 2, 17, 0, 0, 0, 6, 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