Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08fe52115d8b684ab00d3de7d534bb622ecf1ce12d51d7d5dc0cc55196436499

Tx prefix hash: 4338ec4da0207cccd59b45a1783a4821dbe4abe8d3395b37c8322b8260546450
Tx public key: dee64db0c02e176503e6cbb6d31e10ecd4da1cfc6ed4ac3c3792d5410bd03f6f
Timestamp: 1703750197 Timestamp [UCT]: 2023-12-28 07:56:37 Age [y:d:h:m:s]: 01:064:02:27:19
Block: 922839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306894 RingCT/type: yes/0
Extra: 01dee64db0c02e176503e6cbb6d31e10ecd4da1cfc6ed4ac3c3792d5410bd03f6f02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5c83db55a1f28752b394afc9e5b5b7339b7d731dd9373e00898e0ecb25d8ad8 0.600000000000 1380545 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": 922849, "vin": [ { "gen": { "height": 922839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5c83db55a1f28752b394afc9e5b5b7339b7d731dd9373e00898e0ecb25d8ad8" } } ], "extra": [ 1, 222, 230, 77, 176, 192, 46, 23, 101, 3, 230, 203, 182, 211, 30, 16, 236, 212, 218, 28, 252, 110, 212, 172, 60, 55, 146, 213, 65, 11, 208, 63, 111, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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