Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf3717d726348abab21aa113b619d2060cef9f91ec22a1b28c62bceba445e70

Tx prefix hash: f8e97b12adc46da9225f43f4c6db95333eba5f496cb57bd4ce23871eb6c14292
Tx public key: 94c1a7807d3bf5cdc1e240ff477c2761e6383241e3446efbf0f8867e8ea45fba
Timestamp: 1720650340 Timestamp [UCT]: 2024-07-10 22:25:40 Age [y:d:h:m:s]: 00:336:14:01:49
Block: 1062952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240491 RingCT/type: yes/0
Extra: 0194c1a7807d3bf5cdc1e240ff477c2761e6383241e3446efbf0f8867e8ea45fba021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92e50bea3bda8d07f5efa7f778c3b935e127a7c876346bd504b2cb412064caea 0.600000000000 1533463 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": 1062962, "vin": [ { "gen": { "height": 1062952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92e50bea3bda8d07f5efa7f778c3b935e127a7c876346bd504b2cb412064caea" } } ], "extra": [ 1, 148, 193, 167, 128, 125, 59, 245, 205, 193, 226, 64, 255, 71, 124, 39, 97, 230, 56, 50, 65, 227, 68, 110, 251, 240, 248, 134, 126, 142, 164, 95, 186, 2, 17, 0, 0, 0, 1, 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