Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b766f92596811979dd618acca6cdd289acf0c30f8781cd34df71929ad13eeb

Tx prefix hash: 24bef53dd1ac4c227923cfd71ef7e351c75ccb55a2bcaf6474789a39b5fb9d53
Tx public key: 9251612a641c4589523b50973b6f6a2aa4d583e6ca803ef64b784599e14f592d
Timestamp: 1714646534 Timestamp [UCT]: 2024-05-02 10:42:14 Age [y:d:h:m:s]: 00:141:22:59:48
Block: 1013174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101683 RingCT/type: yes/0
Extra: 019251612a641c4589523b50973b6f6a2aa4d583e6ca803ef64b784599e14f592d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 098b51c24b7c6e33e2f805efc1e6896c7958f6a0cee71bd0ea9003ea9b328ecf 0.600000000000 1475921 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": 1013184, "vin": [ { "gen": { "height": 1013174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "098b51c24b7c6e33e2f805efc1e6896c7958f6a0cee71bd0ea9003ea9b328ecf" } } ], "extra": [ 1, 146, 81, 97, 42, 100, 28, 69, 137, 82, 59, 80, 151, 59, 111, 106, 42, 164, 213, 131, 230, 202, 128, 62, 246, 75, 120, 69, 153, 225, 79, 89, 45, 2, 17, 0, 0, 0, 1, 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