Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c1a42fc73a4f7c2de95faa3426f407e1d00d2fd9c78637e8a6134cd43f2030

Tx prefix hash: 7c07975a7c489ddcf33e75866235af095d29b584af880c83f67fe31513557965
Tx public key: 71551645a5b21ed86352a15e0a0c541d52b86bf75dd754c42f317e6f4ad151ee
Timestamp: 1712600459 Timestamp [UCT]: 2024-04-08 18:20:59 Age [y:d:h:m:s]: 01:209:20:20:58
Block: 996177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408678 RingCT/type: yes/0
Extra: 0171551645a5b21ed86352a15e0a0c541d52b86bf75dd754c42f317e6f4ad151ee02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb4409d87b5959c8e8dcf711eba82c5c18ce75afbbc59f5ef2c7a5cb9ccf459 0.600000000000 1456593 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": 996187, "vin": [ { "gen": { "height": 996177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb4409d87b5959c8e8dcf711eba82c5c18ce75afbbc59f5ef2c7a5cb9ccf459" } } ], "extra": [ 1, 113, 85, 22, 69, 165, 178, 30, 216, 99, 82, 161, 94, 10, 12, 84, 29, 82, 184, 107, 247, 93, 215, 84, 196, 47, 49, 126, 111, 74, 209, 81, 238, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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