Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b660952f572f0b7f9ae8ec403f53f9f497438495adaf7fa43d5ca64e9b7a637

Tx prefix hash: d531b94acad868d7fd546d6811b4d90a239d299923d903acfe751ba4c15a5e32
Tx public key: 47526c99d18fb6b4478c3a0513b0e0887648c94ebcd441edcbde6adb65ca864f
Timestamp: 1745093259 Timestamp [UCT]: 2025-04-19 20:07:39 Age [y:d:h:m:s]: 00:035:09:52:55
Block: 1265086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25336 RingCT/type: yes/0
Extra: 0147526c99d18fb6b4478c3a0513b0e0887648c94ebcd441edcbde6adb65ca864f0211000000136c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fec396444b386f121dee51a09035d761313600c0f4d19a9ec223bcd665792d61 0.600000000000 1752289 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": 1265096, "vin": [ { "gen": { "height": 1265086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fec396444b386f121dee51a09035d761313600c0f4d19a9ec223bcd665792d61" } } ], "extra": [ 1, 71, 82, 108, 153, 209, 143, 182, 180, 71, 140, 58, 5, 19, 176, 224, 136, 118, 72, 201, 78, 188, 212, 65, 237, 203, 222, 106, 219, 101, 202, 134, 79, 2, 17, 0, 0, 0, 19, 108, 152, 170, 61, 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