Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d45076445d30596e3b0417996937f822950f7e2c7dab28cd7ff55f01de081b

Tx prefix hash: 919a9d2264348866b14a3cf1f530101219ff3e2f9f08b90e664e014bfb48233a
Tx public key: 3f22f6c26fc2c3169b786abda6a7b5799d059dc570a0796b142f7cb1944ec68b
Timestamp: 1709100687 Timestamp [UCT]: 2024-02-28 06:11:27 Age [y:d:h:m:s]: 01:047:02:55:52
Block: 967199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294692 RingCT/type: yes/0
Extra: 013f22f6c26fc2c3169b786abda6a7b5799d059dc570a0796b142f7cb1944ec68b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 939dd08be6adfcdf775b79599b0d33f5180350064fbf44db42bff7c81818901d 0.600000000000 1426970 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": 967209, "vin": [ { "gen": { "height": 967199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "939dd08be6adfcdf775b79599b0d33f5180350064fbf44db42bff7c81818901d" } } ], "extra": [ 1, 63, 34, 246, 194, 111, 194, 195, 22, 155, 120, 106, 189, 166, 167, 181, 121, 157, 5, 157, 197, 112, 160, 121, 107, 20, 47, 124, 177, 148, 78, 198, 139, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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