Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c92e0c19d0ef0ff46688ab41f169de3c7feb3a11722cf8f5edf584e3b21531b6

Tx prefix hash: fb5c6c2e0403a41d576f6af692ed679871af8f4026cec88517235ad6f3e10da9
Tx public key: 8bbd2567c2bd5d0b3acd26b3ae9c23e3e20bb1ecb42186dd2c50420dc6af2950
Timestamp: 1695632533 Timestamp [UCT]: 2023-09-25 09:02:13 Age [y:d:h:m:s]: 01:192:06:15:41
Block: 855739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398472 RingCT/type: yes/0
Extra: 018bbd2567c2bd5d0b3acd26b3ae9c23e3e20bb1ecb42186dd2c50420dc6af29500211000000021656a529000000000000000000

1 output(s) for total of 0.896564435000 dcy

stealth address amount amount idx
00: f212935855ba10156a9c0eb9ef1143a840741d2f1ffc249485133dd8b40515dd 0.896564435000 1309777 of 0

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": 855749, "vin": [ { "gen": { "height": 855739 } } ], "vout": [ { "amount": 896564435, "target": { "key": "f212935855ba10156a9c0eb9ef1143a840741d2f1ffc249485133dd8b40515dd" } } ], "extra": [ 1, 139, 189, 37, 103, 194, 189, 93, 11, 58, 205, 38, 179, 174, 156, 35, 227, 226, 11, 177, 236, 180, 33, 134, 221, 44, 80, 66, 13, 198, 175, 41, 80, 2, 17, 0, 0, 0, 2, 22, 86, 165, 41, 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