Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c03e0049286fea72ee687b1a390c243c4c539f82d55e6a80d8468b4240756b3

Tx prefix hash: d259b973b979d32f1d9c187df4e45a1300be26a3619ea7b88988578ecbe27bb3
Tx public key: 0cac98a6c6ad7e8c74686a5b55071d777114cc87a272f4c631b8ab01e62ee6bb
Timestamp: 1728717173 Timestamp [UCT]: 2024-10-12 07:12:53 Age [y:d:h:m:s]: 00:103:07:24:30
Block: 1129824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73811 RingCT/type: yes/0
Extra: 010cac98a6c6ad7e8c74686a5b55071d777114cc87a272f4c631b8ab01e62ee6bb02110000000591e13c04000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 0db22207af6cba3f5267cf4a095f8729b6ac74d378400e23b145c92cf20bfdd8 0.600010000000 1612691 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": 1129834, "vin": [ { "gen": { "height": 1129824 } } ], "vout": [ { "amount": 600010000, "target": { "key": "0db22207af6cba3f5267cf4a095f8729b6ac74d378400e23b145c92cf20bfdd8" } } ], "extra": [ 1, 12, 172, 152, 166, 198, 173, 126, 140, 116, 104, 106, 91, 85, 7, 29, 119, 113, 20, 204, 135, 162, 114, 244, 198, 49, 184, 171, 1, 230, 46, 230, 187, 2, 17, 0, 0, 0, 5, 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