Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c06caf861eae980bc1bcf2d99868642b77edc3f7ff39a3eacc41dff8353c919

Tx prefix hash: 8c74637b40aaf633dd0f76702c5931af712d2a53e10ce4bfd117c072a7d35681
Tx public key: 81b910c6a7f8d7bf03d39382e382b81beb084b325ce126dfafe7883aa4e58220
Timestamp: 1746477140 Timestamp [UCT]: 2025-05-05 20:32:20 Age [y:d:h:m:s]: 00:149:23:12:53
Block: 1276533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104831 RingCT/type: yes/0
Extra: 0181b910c6a7f8d7bf03d39382e382b81beb084b325ce126dfafe7883aa4e582200211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 185e9dd4a46818ec260a1bb96a214bfa05b92efc53b92810661c81122d24a5e3 0.600000000000 1763880 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": 1276543, "vin": [ { "gen": { "height": 1276533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "185e9dd4a46818ec260a1bb96a214bfa05b92efc53b92810661c81122d24a5e3" } } ], "extra": [ 1, 129, 185, 16, 198, 167, 248, 215, 191, 3, 211, 147, 130, 227, 130, 184, 27, 235, 8, 75, 50, 92, 225, 38, 223, 175, 231, 136, 58, 164, 229, 130, 32, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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