Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad0c32fb2bd1783da1f4943e85a1587a4ed851117203b4c66218f033ae8d203

Tx prefix hash: 9079e5a996e5f3e387c1769f52148c9b3481280676467a664ae915d1b2069c7a
Tx public key: 3b903751f43ff3a5c0cf63a4c1678a448bdb62349df9a3cbc1825bd350c828d3
Timestamp: 1735369138 Timestamp [UCT]: 2024-12-28 06:58:58 Age [y:d:h:m:s]: 00:092:17:55:52
Block: 1184849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66067 RingCT/type: yes/0
Extra: 013b903751f43ff3a5c0cf63a4c1678a448bdb62349df9a3cbc1825bd350c828d30211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63f12ab33240dfa7c2825305c0d93a89f9b8a521004135a91749f91c68cd58d9 0.600000000000 1671308 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": 1184859, "vin": [ { "gen": { "height": 1184849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63f12ab33240dfa7c2825305c0d93a89f9b8a521004135a91749f91c68cd58d9" } } ], "extra": [ 1, 59, 144, 55, 81, 244, 63, 243, 165, 192, 207, 99, 164, 193, 103, 138, 68, 139, 219, 98, 52, 157, 249, 163, 203, 193, 130, 91, 211, 80, 200, 40, 211, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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