Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19204d7966fb08c5d079106d2a45db3b11f2f0db1a7e8caa28f19fbad44bccea

Tx prefix hash: 775b05b3269f16aeea2f84ea6e67ba7f42f7c1fd7c6e8b679f0333ca56ad3c3e
Tx public key: fcbe4577a961dc14553f10cb77abce49d617b27d77a4b43dbecc9f5952000252
Timestamp: 1735892918 Timestamp [UCT]: 2025-01-03 08:28:38 Age [y:d:h:m:s]: 00:112:14:34:07
Block: 1189211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80230 RingCT/type: yes/0
Extra: 01fcbe4577a961dc14553f10cb77abce49d617b27d77a4b43dbecc9f59520002520211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e550774542760392f422a3c89376b081ad456bbda6b070622ea12dfed87fe6aa 0.600000000000 1675716 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": 1189221, "vin": [ { "gen": { "height": 1189211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e550774542760392f422a3c89376b081ad456bbda6b070622ea12dfed87fe6aa" } } ], "extra": [ 1, 252, 190, 69, 119, 169, 97, 220, 20, 85, 63, 16, 203, 119, 171, 206, 73, 214, 23, 178, 125, 119, 164, 180, 61, 190, 204, 159, 89, 82, 0, 2, 82, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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