Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac89580f4d09f2c35210d6f3cb4ae2e77a9dc9437754c2f5c85906d09c13145

Tx prefix hash: 45030e2e1cb1f7299bf8cb296ea406ad13b079d4197ed6d6b277c13edb04878e
Tx public key: 2baee9e9dec7f4c660124cdf36bbdd56cf20e8ed5008d9853220fe7a2f2f08b7
Timestamp: 1713985837 Timestamp [UCT]: 2024-04-24 19:10:37 Age [y:d:h:m:s]: 00:341:11:06:10
Block: 1007693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244099 RingCT/type: yes/0
Extra: 012baee9e9dec7f4c660124cdf36bbdd56cf20e8ed5008d9853220fe7a2f2f08b702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0769657be27f7479bd5bbad802ac30b7c0e4e5fb280b05ab8d36e180e81441fd 0.600000000000 1469117 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": 1007703, "vin": [ { "gen": { "height": 1007693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0769657be27f7479bd5bbad802ac30b7c0e4e5fb280b05ab8d36e180e81441fd" } } ], "extra": [ 1, 43, 174, 233, 233, 222, 199, 244, 198, 96, 18, 76, 223, 54, 187, 221, 86, 207, 32, 232, 237, 80, 8, 217, 133, 50, 32, 254, 122, 47, 47, 8, 183, 2, 17, 0, 0, 0, 1, 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