Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 422ad139df2d428716a84df34f0f99e39aff5e2fc4b1652a3e9b736f61993dd5

Tx prefix hash: 9311250a959d915ec000c0570356e112df5994436956e13308e53c77482a740e
Tx public key: 769fb1249c05a138309f0d78aa0dea3b460d10ca7772bcaaf8ba6c880978b482
Timestamp: 1635315232 Timestamp [UCT]: 2021-10-27 06:13:52 Age [y:d:h:m:s]: 04:005:13:57:24
Block: 361371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1040790 RingCT/type: yes/0
Extra: 01769fb1249c05a138309f0d78aa0dea3b460d10ca7772bcaaf8ba6c880978b48202110000003a1154028c000000000000000000

1 output(s) for total of 38.961936407000 dcy

stealth address amount amount idx
00: a84f2fa49236dc9b9e45542ab07c1d1b51d716d9a899a8fa984f0ff0418bf8bc 38.961936407000 735227 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": 361381, "vin": [ { "gen": { "height": 361371 } } ], "vout": [ { "amount": 38961936407, "target": { "key": "a84f2fa49236dc9b9e45542ab07c1d1b51d716d9a899a8fa984f0ff0418bf8bc" } } ], "extra": [ 1, 118, 159, 177, 36, 156, 5, 161, 56, 48, 159, 13, 120, 170, 13, 234, 59, 70, 13, 16, 202, 119, 114, 188, 170, 248, 186, 108, 136, 9, 120, 180, 130, 2, 17, 0, 0, 0, 58, 17, 84, 2, 140, 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