Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f040714ba6f5f9253384387b68a1a1ce6388673fcbc1ffdf9196d10f9400000

Tx prefix hash: f1d10aa44789916da28b606d23dc52509467ca130d173e9190f8de41ddddbfa3
Tx public key: f718ba8968c5cd41a43f1d5881c6ef74fda53a273cbe30eed0de6b638d7e62e1
Timestamp: 1694237594 Timestamp [UCT]: 2023-09-09 05:33:14 Age [y:d:h:m:s]: 01:207:20:43:09
Block: 844150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409660 RingCT/type: yes/0
Extra: 01f718ba8968c5cd41a43f1d5881c6ef74fda53a273cbe30eed0de6b638d7e62e10211000000064b8f5122000000000000000000

1 output(s) for total of 0.979446440000 dcy

stealth address amount amount idx
00: 5a70d8a4abe6c7b08aec9a3e0402c74173f8da961480127997a82c93a502cec4 0.979446440000 1297440 of 0

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": 844160, "vin": [ { "gen": { "height": 844150 } } ], "vout": [ { "amount": 979446440, "target": { "key": "5a70d8a4abe6c7b08aec9a3e0402c74173f8da961480127997a82c93a502cec4" } } ], "extra": [ 1, 247, 24, 186, 137, 104, 197, 205, 65, 164, 63, 29, 88, 129, 198, 239, 116, 253, 165, 58, 39, 60, 190, 48, 238, 208, 222, 107, 99, 141, 126, 98, 225, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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