Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334037a77de47a503867d8edb0a358dd952b32dd5cecd335d4b0c867555524f3

Tx prefix hash: 0f206147eaa89b87e5127ae10a9de96e99d3f8ffec59b35c8c0b5dfe2315c358
Tx public key: 97cc9d7f81346f5165cba921182b29d3b5379c0c89f23400146c7a685f0eae07
Timestamp: 1677102935 Timestamp [UCT]: 2023-02-22 21:55:35 Age [y:d:h:m:s]: 02:055:00:08:20
Block: 702798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560898 RingCT/type: yes/0
Extra: 0197cc9d7f81346f5165cba921182b29d3b5379c0c89f23400146c7a685f0eae07021100000001272bcc39000000000000000000

1 output(s) for total of 2.879641275000 dcy

stealth address amount amount idx
00: 63476287911016ef2d586eea3392c1b3435140b08c5121bed2c0e53b7c430022 2.879641275000 1146345 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": 702808, "vin": [ { "gen": { "height": 702798 } } ], "vout": [ { "amount": 2879641275, "target": { "key": "63476287911016ef2d586eea3392c1b3435140b08c5121bed2c0e53b7c430022" } } ], "extra": [ 1, 151, 204, 157, 127, 129, 52, 111, 81, 101, 203, 169, 33, 24, 43, 41, 211, 181, 55, 156, 12, 137, 242, 52, 0, 20, 108, 122, 104, 95, 14, 174, 7, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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