Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e292448929d353b7842281373998c3ab3c6068cb64521db64afbd51bab499f5a

Tx prefix hash: 795fbb985fbe7e77bcbddd90ca663697501484c718c99133a66a7d25b2c200f3
Tx public key: fad93fa52a40aafec5c122077f08d7e6a072bbeb5780285e89e24f4b3a087abf
Timestamp: 1577813778 Timestamp [UCT]: 2019-12-31 17:36:18 Age [y:d:h:m:s]: 04:364:23:16:53
Block: 35918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149935 RingCT/type: yes/0
Extra: 01fad93fa52a40aafec5c122077f08d7e6a072bbeb5780285e89e24f4b3a087abf021100000089c3a1a09f000000000000000000

1 output(s) for total of 466.648215449000 dcy

stealth address amount amount idx
00: b18f18099dd73809acaccd76b6b8eb356a8c411c2e558af86dc39b6af0ee0891 466.648215449000 60660 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": 35928, "vin": [ { "gen": { "height": 35918 } } ], "vout": [ { "amount": 466648215449, "target": { "key": "b18f18099dd73809acaccd76b6b8eb356a8c411c2e558af86dc39b6af0ee0891" } } ], "extra": [ 1, 250, 217, 63, 165, 42, 64, 170, 254, 197, 193, 34, 7, 127, 8, 215, 230, 160, 114, 187, 235, 87, 128, 40, 94, 137, 226, 79, 75, 58, 8, 122, 191, 2, 17, 0, 0, 0, 137, 195, 161, 160, 159, 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