Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f5e0c35b5e21c430ca94b8dbb89cf4cdc6236f652015801a0a23d97630574a

Tx prefix hash: 7740d560e8e1228dcbfeb4c7fddf2c55584a94d77e306c3fd64651b429459826
Tx public key: 983b94692fd677e2fa5ea2c69456ecbb55b4b326938cc7ea359011e72cfa1ec7
Timestamp: 1714230526 Timestamp [UCT]: 2024-04-27 15:08:46 Age [y:d:h:m:s]: 00:256:06:41:51
Block: 1009722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183431 RingCT/type: yes/0
Extra: 01983b94692fd677e2fa5ea2c69456ecbb55b4b326938cc7ea359011e72cfa1ec702110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa69ef4615ea79bcceef8ddbd62853dae6339dd96a5350f6f7e5f94ea61ff338 0.600000000000 1471474 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": 1009732, "vin": [ { "gen": { "height": 1009722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa69ef4615ea79bcceef8ddbd62853dae6339dd96a5350f6f7e5f94ea61ff338" } } ], "extra": [ 1, 152, 59, 148, 105, 47, 214, 119, 226, 250, 94, 162, 198, 148, 86, 236, 187, 85, 180, 179, 38, 147, 140, 199, 234, 53, 144, 17, 231, 44, 250, 30, 199, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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