Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01626808a382ee4297bd4a7db9b40b659d855463d22c94f742710a6d21e924f3

Tx prefix hash: 1f283cfe0b0782157627fa2081cd8deecaf47e8a35eb7cbf018e4f438295ee79
Tx public key: e41c9aa7e3a1748443198fcefb1537a1a2f33aeae8ea35c699d2a4b7abb8a6f1
Timestamp: 1707632196 Timestamp [UCT]: 2024-02-11 06:16:36 Age [y:d:h:m:s]: 01:065:23:27:56
Block: 955012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308207 RingCT/type: yes/0
Extra: 01e41c9aa7e3a1748443198fcefb1537a1a2f33aeae8ea35c699d2a4b7abb8a6f102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d259f8d86d8f5c8e48ba93f6fbe32d3d37636406a518000b0fc371d31e9f970a 0.600000000000 1414294 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": 955022, "vin": [ { "gen": { "height": 955012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d259f8d86d8f5c8e48ba93f6fbe32d3d37636406a518000b0fc371d31e9f970a" } } ], "extra": [ 1, 228, 28, 154, 167, 227, 161, 116, 132, 67, 25, 143, 206, 251, 21, 55, 161, 162, 243, 58, 234, 232, 234, 53, 198, 153, 210, 164, 183, 171, 184, 166, 241, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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