Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e3fdb4180c43b0e99834829bc45b4a2df3bfce7f7cb12c55f13ac84378f7766

Tx prefix hash: b49acf0b6a96ddbb007a5607bdc0549995be1fe6cd7cf5430f92197944ddfeda
Tx public key: 5a832f2503148ecbeda6f3a22c145b4e1e4c134e4bf6e762cc21daf6a2ba1a7d
Timestamp: 1735822614 Timestamp [UCT]: 2025-01-02 12:56:54 Age [y:d:h:m:s]: 00:307:11:42:41
Block: 1188603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217247 RingCT/type: yes/0
Extra: 015a832f2503148ecbeda6f3a22c145b4e1e4c134e4bf6e762cc21daf6a2ba1a7d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78eb620ef1acf096ecdce246fd0181bec0bcfa731a8aa4745290e1d3ffa9bdf8 0.600000000000 1675106 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": 1188613, "vin": [ { "gen": { "height": 1188603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78eb620ef1acf096ecdce246fd0181bec0bcfa731a8aa4745290e1d3ffa9bdf8" } } ], "extra": [ 1, 90, 131, 47, 37, 3, 20, 142, 203, 237, 166, 243, 162, 44, 20, 91, 78, 30, 76, 19, 78, 75, 246, 231, 98, 204, 33, 218, 246, 162, 186, 26, 125, 2, 17, 0, 0, 0, 2, 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