Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c5d5d24b57804253c89b205aa8f8d9ce4df9fcfb878578624b8601fe771263

Tx prefix hash: 79809a5f143dae81b21f3bcc1b0d54fc44c5ca56b0de647a62a6736142adccac
Tx public key: 03defb62005caf29ea510f3e66e2a980fd63526fd094340623c14ac09c70f816
Timestamp: 1710554346 Timestamp [UCT]: 2024-03-16 01:59:06 Age [y:d:h:m:s]: 01:020:06:02:35
Block: 979263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275448 RingCT/type: yes/0
Extra: 0103defb62005caf29ea510f3e66e2a980fd63526fd094340623c14ac09c70f8160211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84d42a37b324b600e693b60b5a2928361af3b74f666d1f54d9fe0056b97ad866 0.600000000000 1439296 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": 979273, "vin": [ { "gen": { "height": 979263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84d42a37b324b600e693b60b5a2928361af3b74f666d1f54d9fe0056b97ad866" } } ], "extra": [ 1, 3, 222, 251, 98, 0, 92, 175, 41, 234, 81, 15, 62, 102, 226, 169, 128, 253, 99, 82, 111, 208, 148, 52, 6, 35, 193, 74, 192, 156, 112, 248, 22, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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