Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3066d719dd199cde4391972ca105262dc778433bf9a8b1d546b92e7fd5b8e9dc

Tx prefix hash: 8c3f6a9cbb0b9600e084924ec7e98e16a923a304ba0c6efaf8b1820433ff7214
Tx public key: 982506f49f6c21890e7af415993b50f698ad679d718ce35b184a27b47edf3d77
Timestamp: 1728525289 Timestamp [UCT]: 2024-10-10 01:54:49 Age [y:d:h:m:s]: 00:183:06:48:48
Block: 1128230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130791 RingCT/type: yes/0
Extra: 01982506f49f6c21890e7af415993b50f698ad679d718ce35b184a27b47edf3d7702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4acf5d9099c32971214dc7c62c5c81f5bb8e103c5348c455cbbcb2465e4f80f 0.600000000000 1611047 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": 1128240, "vin": [ { "gen": { "height": 1128230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4acf5d9099c32971214dc7c62c5c81f5bb8e103c5348c455cbbcb2465e4f80f" } } ], "extra": [ 1, 152, 37, 6, 244, 159, 108, 33, 137, 14, 122, 244, 21, 153, 59, 80, 246, 152, 173, 103, 157, 113, 140, 227, 91, 24, 74, 39, 180, 126, 223, 61, 119, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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