Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 769950ff61f0267c4b83ae630ae6fec7e3263ec673ed8a9dad966253102cd32b

Tx prefix hash: 294ae7924037c8c48b09db8d96e13cfac3cc55fc43f37df18e4fd380032ab3ac
Tx public key: c0dd11a5dbce246795b1b699d69a9ed266d0a158b092e2df15b360bae77bd89c
Timestamp: 1720841189 Timestamp [UCT]: 2024-07-13 03:26:29 Age [y:d:h:m:s]: 00:330:04:35:28
Block: 1064539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235956 RingCT/type: yes/0
Extra: 01c0dd11a5dbce246795b1b699d69a9ed266d0a158b092e2df15b360bae77bd89c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21ddaca49b08e48b7fa1629d8db067157e99eb1c6574d338cb885d9ffddd6306 0.600000000000 1535068 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": 1064549, "vin": [ { "gen": { "height": 1064539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21ddaca49b08e48b7fa1629d8db067157e99eb1c6574d338cb885d9ffddd6306" } } ], "extra": [ 1, 192, 221, 17, 165, 219, 206, 36, 103, 149, 177, 182, 153, 214, 154, 158, 210, 102, 208, 161, 88, 176, 146, 226, 223, 21, 179, 96, 186, 231, 123, 216, 156, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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