Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2802bd640ca5fa626b450e4f0af5c43dd4c7144efc2223c04cb40901bac1a36

Tx prefix hash: ffe849d6c886a07b17851516feff8c922aa931b7c85bf0d97edffcfef2317a33
Tx public key: ba9b40facaec86fdaac71eb08e8f9bea3fcaede0d7f78d146d62f193e2c1925e
Timestamp: 1735120942 Timestamp [UCT]: 2024-12-25 10:02:22 Age [y:d:h:m:s]: 00:096:04:51:05
Block: 1182797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68530 RingCT/type: yes/0
Extra: 01ba9b40facaec86fdaac71eb08e8f9bea3fcaede0d7f78d146d62f193e2c1925e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4a14600f9f1309bc592495edbbe781639a101403caae40a9b7bf2ef33eecfb4 0.600000000000 1669236 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": 1182807, "vin": [ { "gen": { "height": 1182797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4a14600f9f1309bc592495edbbe781639a101403caae40a9b7bf2ef33eecfb4" } } ], "extra": [ 1, 186, 155, 64, 250, 202, 236, 134, 253, 170, 199, 30, 176, 142, 143, 155, 234, 63, 202, 237, 224, 215, 247, 141, 20, 109, 98, 241, 147, 226, 193, 146, 94, 2, 17, 0, 0, 0, 6, 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