Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d7bb5b7c68e4d3686dcec74efbd84ea8242043dad84069751e49824e82704e

Tx prefix hash: e6b0f1e299f31d0c39617934966cbcf130eff13d694da1ecd768bf1f2fd4051c
Tx public key: 94cff3e6f066f436d1e684e810a028041b7095e3447c43c4ea7333370b8eced8
Timestamp: 1705872953 Timestamp [UCT]: 2024-01-21 21:35:53 Age [y:d:h:m:s]: 01:128:00:43:51
Block: 940399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352651 RingCT/type: yes/0
Extra: 0194cff3e6f066f436d1e684e810a028041b7095e3447c43c4ea7333370b8eced802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d31832098902079e787c54455045e2ab4d1c30c62329e710db3fa45c78651192 0.600000000000 1398535 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": 940409, "vin": [ { "gen": { "height": 940399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d31832098902079e787c54455045e2ab4d1c30c62329e710db3fa45c78651192" } } ], "extra": [ 1, 148, 207, 243, 230, 240, 102, 244, 54, 209, 230, 132, 232, 16, 160, 40, 4, 27, 112, 149, 227, 68, 124, 67, 196, 234, 115, 51, 55, 11, 142, 206, 216, 2, 17, 0, 0, 0, 2, 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