Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82ac0da569502778a8fddcc4d969b446736af288d87d557035de3315e5caf428

Tx prefix hash: 5ca822bd1afd14fac454807b429f2fd8a5c96acab60e81eac78b06497846e355
Tx public key: 71fc35e81035925c5e15f5afec47d5cc882ee97217a5ede24cebc2b6dc3f77cb
Timestamp: 1727409097 Timestamp [UCT]: 2024-09-27 03:51:37 Age [y:d:h:m:s]: 00:106:16:17:04
Block: 1118984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76264 RingCT/type: yes/0
Extra: 0171fc35e81035925c5e15f5afec47d5cc882ee97217a5ede24cebc2b6dc3f77cb021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19be3aa7f1bae4e903af4cb5175b7b550ea74fa14bea9d05631ba3cdc695f7c9 0.600000000000 1600367 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": 1118994, "vin": [ { "gen": { "height": 1118984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19be3aa7f1bae4e903af4cb5175b7b550ea74fa14bea9d05631ba3cdc695f7c9" } } ], "extra": [ 1, 113, 252, 53, 232, 16, 53, 146, 92, 94, 21, 245, 175, 236, 71, 213, 204, 136, 46, 233, 114, 23, 165, 237, 226, 76, 235, 194, 182, 220, 63, 119, 203, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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