Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d17ca02b4d1cc7b2fb3fbae3e3dcc11faac8d4b888d3f67d601fe579ad6d2c90

Tx prefix hash: 50c244486ce14cc16ba9267ebd0f32928df29951decd3bbfca44905fce8424fe
Tx public key: a696eddbd4adf534a83b0cd8264179431c9d42e820766842b64131b5df354b18
Timestamp: 1708805728 Timestamp [UCT]: 2024-02-24 20:15:28 Age [y:d:h:m:s]: 00:320:17:03:55
Block: 964751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229582 RingCT/type: yes/0
Extra: 01a696eddbd4adf534a83b0cd8264179431c9d42e820766842b64131b5df354b1802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddefb2a2c3c5dc9a4509d6ac992ea5807d1521f6e1bb8cb13e24fbc20c546986 0.600000000000 1424494 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": 964761, "vin": [ { "gen": { "height": 964751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddefb2a2c3c5dc9a4509d6ac992ea5807d1521f6e1bb8cb13e24fbc20c546986" } } ], "extra": [ 1, 166, 150, 237, 219, 212, 173, 245, 52, 168, 59, 12, 216, 38, 65, 121, 67, 28, 157, 66, 232, 32, 118, 104, 66, 182, 65, 49, 181, 223, 53, 75, 24, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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