Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68b33407ff84a2f224a1e93df3074aec157d46c813c199b3b16cddcb536f7941

Tx prefix hash: fefb70fbe0b815f0bdc8a0be0c8bec9056f08352a4deffa54c634c2ea2c4dacd
Tx public key: 9922c0a38a905e4a680a2db468adf2617025a443d106e8a4c5f4933355dba9ba
Timestamp: 1707081369 Timestamp [UCT]: 2024-02-04 21:16:09 Age [y:d:h:m:s]: 01:023:22:14:10
Block: 950442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278132 RingCT/type: yes/0
Extra: 019922c0a38a905e4a680a2db468adf2617025a443d106e8a4c5f4933355dba9ba021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 562dc9b680be4d20abb3e767bd419efb2161b1502ea77d87fd8269fb7f48a748 0.600000000000 1409066 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": 950452, "vin": [ { "gen": { "height": 950442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "562dc9b680be4d20abb3e767bd419efb2161b1502ea77d87fd8269fb7f48a748" } } ], "extra": [ 1, 153, 34, 192, 163, 138, 144, 94, 74, 104, 10, 45, 180, 104, 173, 242, 97, 112, 37, 164, 67, 209, 6, 232, 164, 197, 244, 147, 51, 85, 219, 169, 186, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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