Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef52c052d4f2bdcfeabf8edc5b3cd2362f7c3134bd5b4aeda1f1f893bcec21d3

Tx prefix hash: 68dd2b94c675188d11dec2c3bf1546a359a9021c7b4f72bb4ff6d2d04563814f
Tx public key: e8352ed721f585a80f6829c47cad7fe71c56f9fd21e32b26bb75244a5ab050b1
Timestamp: 1718729022 Timestamp [UCT]: 2024-06-18 16:43:42 Age [y:d:h:m:s]: 00:340:22:31:15
Block: 1047014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243686 RingCT/type: yes/0
Extra: 01e8352ed721f585a80f6829c47cad7fe71c56f9fd21e32b26bb75244a5ab050b102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 300a79fd9890b9be613c0bbac9e2a870f179960f24de8e39ceba0d59cc6d2568 0.600000000000 1516833 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": 1047024, "vin": [ { "gen": { "height": 1047014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "300a79fd9890b9be613c0bbac9e2a870f179960f24de8e39ceba0d59cc6d2568" } } ], "extra": [ 1, 232, 53, 46, 215, 33, 245, 133, 168, 15, 104, 41, 196, 124, 173, 127, 231, 28, 86, 249, 253, 33, 227, 43, 38, 187, 117, 36, 74, 90, 176, 80, 177, 2, 17, 0, 0, 0, 3, 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