Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93441b30a8c17ba2d8921302a44fc9634bd428f428acee1fcf86a9d4187c7fbf

Tx prefix hash: a37b2b524f0e8e8d3e92318ca8a05dc4ec0d30680a11021f9ecc47fed09f606a
Tx public key: 1d94b6610aca0c9aa81295229e1fdcf4630e5d9a9a18502454231ae8bfcc39ef
Timestamp: 1728442256 Timestamp [UCT]: 2024-10-09 02:50:56 Age [y:d:h:m:s]: 00:183:09:50:32
Block: 1127544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130878 RingCT/type: yes/0
Extra: 011d94b6610aca0c9aa81295229e1fdcf4630e5d9a9a18502454231ae8bfcc39ef02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 705d494b68310a0a9dbedd6eedc21b82c253af6f12ff115da7c5176b53144cde 0.600000000000 1610351 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": 1127554, "vin": [ { "gen": { "height": 1127544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "705d494b68310a0a9dbedd6eedc21b82c253af6f12ff115da7c5176b53144cde" } } ], "extra": [ 1, 29, 148, 182, 97, 10, 202, 12, 154, 168, 18, 149, 34, 158, 31, 220, 244, 99, 14, 93, 154, 154, 24, 80, 36, 84, 35, 26, 232, 191, 204, 57, 239, 2, 17, 0, 0, 0, 6, 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