Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9e7dea65be1addf793468af50705030dd56e693379e980b6ab629224a6d63f

Tx prefix hash: 5fef4697b5595c700772cc919e23b5fa6176e50d6b83ceb9d0e6d8baa6026524
Tx public key: 1429e7c0d3c861a6868bfaad2b49748f0e5dec86cadd67bbfa8a3a993b267f8b
Timestamp: 1707536377 Timestamp [UCT]: 2024-02-10 03:39:37 Age [y:d:h:m:s]: 01:017:16:14:27
Block: 954211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273657 RingCT/type: yes/0
Extra: 011429e7c0d3c861a6868bfaad2b49748f0e5dec86cadd67bbfa8a3a993b267f8b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceebabecf979893eb3b65cf7a20693f7b17bd2763eb1aba820e72d0802ed7b64 0.600000000000 1413487 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": 954221, "vin": [ { "gen": { "height": 954211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceebabecf979893eb3b65cf7a20693f7b17bd2763eb1aba820e72d0802ed7b64" } } ], "extra": [ 1, 20, 41, 231, 192, 211, 200, 97, 166, 134, 139, 250, 173, 43, 73, 116, 143, 14, 93, 236, 134, 202, 221, 103, 187, 250, 138, 58, 153, 59, 38, 127, 139, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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