Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ca99286888c62378ba1c8cf2f29c306bb0579dc724af8b50f544acb52d2d28

Tx prefix hash: 40cfa90f73ff389095b34e5cf948adbab75814148c199c8f2c8a814d4f797bed
Tx public key: 1b6430b007af1a5f785bb28803787f9eb5d84609f52383df6c73c643d0381f85
Timestamp: 1716551466 Timestamp [UCT]: 2024-05-24 11:51:06 Age [y:d:h:m:s]: 01:022:16:10:12
Block: 1028981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277012 RingCT/type: yes/0
Extra: 011b6430b007af1a5f785bb28803787f9eb5d84609f52383df6c73c643d0381f850211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8af714d86d3e056237d9611f27e712e3f4251b8d13fe1b79a81bc9e5cbe4ac46 0.600000000000 1496982 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": 1028991, "vin": [ { "gen": { "height": 1028981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8af714d86d3e056237d9611f27e712e3f4251b8d13fe1b79a81bc9e5cbe4ac46" } } ], "extra": [ 1, 27, 100, 48, 176, 7, 175, 26, 95, 120, 91, 178, 136, 3, 120, 127, 158, 181, 216, 70, 9, 245, 35, 131, 223, 108, 115, 198, 67, 208, 56, 31, 133, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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