Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82159b4d88e453f0078b68c336c729aba13bb133a063e7d052c43af1e4943e46

Tx prefix hash: 9ce79ee5b9c10373647c1dfc90e57e4c0e3efa3ab38dedb812d3837a920a58e1
Tx public key: ca57a15a26daabc770e9f31c993586feaf0f0c468e49ce4d94277e59a02f05b8
Timestamp: 1735837105 Timestamp [UCT]: 2025-01-02 16:58:25 Age [y:d:h:m:s]: 00:167:06:45:06
Block: 1188721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119253 RingCT/type: yes/0
Extra: 01ca57a15a26daabc770e9f31c993586feaf0f0c468e49ce4d94277e59a02f05b80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96cd8af123760b9d820e5afaf90d891fbc7c68f0162546bd57c97c30f18f87cb 0.600000000000 1675224 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": 1188731, "vin": [ { "gen": { "height": 1188721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96cd8af123760b9d820e5afaf90d891fbc7c68f0162546bd57c97c30f18f87cb" } } ], "extra": [ 1, 202, 87, 161, 90, 38, 218, 171, 199, 112, 233, 243, 28, 153, 53, 134, 254, 175, 15, 12, 70, 142, 73, 206, 77, 148, 39, 126, 89, 160, 47, 5, 184, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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