Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06a11916df9f79350f46adf11ab50d777bbee169d3c818ea6e693bb63ecc44d0

Tx prefix hash: 11dfc2df25d3ac9d608bce377e6b2fdb5c22322823733e0fb39e9fee5317cf40
Tx public key: 346449ef0266b9423d99b7957a6c7fadca43be3a83ba02be8622a89f98e493fe
Timestamp: 1684920770 Timestamp [UCT]: 2023-05-24 09:32:50 Age [y:d:h:m:s]: 01:320:06:58:34
Block: 766987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490118 RingCT/type: yes/0
Extra: 01346449ef0266b9423d99b7957a6c7fadca43be3a83ba02be8622a89f98e493fe02110000000633af99f4000000000000000000

1 output(s) for total of 1.764630803000 dcy

stealth address amount amount idx
00: be249a7f40ea17c02f8f6103b8633dd86c44b3e95bcf668a7981bf3c08a6ca46 1.764630803000 1216068 of 0

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": 766997, "vin": [ { "gen": { "height": 766987 } } ], "vout": [ { "amount": 1764630803, "target": { "key": "be249a7f40ea17c02f8f6103b8633dd86c44b3e95bcf668a7981bf3c08a6ca46" } } ], "extra": [ 1, 52, 100, 73, 239, 2, 102, 185, 66, 61, 153, 183, 149, 122, 108, 127, 173, 202, 67, 190, 58, 131, 186, 2, 190, 134, 34, 168, 159, 152, 228, 147, 254, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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