Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 423a52f03979671b24a4941c370bae6fa20db6b5806e8c0d7e84b2089195efe1

Tx prefix hash: 1e51313c0ddcac00b1dd7ec187045ce8471abe100b45957b0847bdd63b73c194
Tx public key: 2cefee41527021934ff4880d1d8709c40af2b568b11292ccb2b5a2a907f30243
Timestamp: 1707574056 Timestamp [UCT]: 2024-02-10 14:07:36 Age [y:d:h:m:s]: 01:273:05:31:44
Block: 954529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454054 RingCT/type: yes/0
Extra: 012cefee41527021934ff4880d1d8709c40af2b568b11292ccb2b5a2a907f3024302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f526bb2c93086d545aa60e88b8f5cfb61ea1eb01c7573b53ca074c0f37d2f8de 0.600000000000 1413809 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": 954539, "vin": [ { "gen": { "height": 954529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f526bb2c93086d545aa60e88b8f5cfb61ea1eb01c7573b53ca074c0f37d2f8de" } } ], "extra": [ 1, 44, 239, 238, 65, 82, 112, 33, 147, 79, 244, 136, 13, 29, 135, 9, 196, 10, 242, 181, 104, 177, 18, 146, 204, 178, 181, 162, 169, 7, 243, 2, 67, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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