Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93f03c09c6d9b3f66c5ccff8f7bf96f5e8c3dd20694c734c84d5f5abbeff4334

Tx prefix hash: 246a502594ca3c93cec09dda168be2217fda04c6932ebcad14f0e40e0ae7b3c2
Tx public key: 2f70f8d60df24dba32a204babf535c69ecb4e547ae88610475a49c421fd2edac
Timestamp: 1716660485 Timestamp [UCT]: 2024-05-25 18:08:05 Age [y:d:h:m:s]: 00:241:18:56:27
Block: 1029881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172992 RingCT/type: yes/0
Extra: 012f70f8d60df24dba32a204babf535c69ecb4e547ae88610475a49c421fd2edac02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c2dc77cac1b8d64a73558f0f48d135db0f0766866f0d9e6015f2676447fb693 0.600000000000 1498088 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": 1029891, "vin": [ { "gen": { "height": 1029881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2dc77cac1b8d64a73558f0f48d135db0f0766866f0d9e6015f2676447fb693" } } ], "extra": [ 1, 47, 112, 248, 214, 13, 242, 77, 186, 50, 162, 4, 186, 191, 83, 92, 105, 236, 180, 229, 71, 174, 136, 97, 4, 117, 164, 156, 66, 31, 210, 237, 172, 2, 17, 0, 0, 0, 5, 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