Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 089f5cdc8116f3f2730f508462edf747edc47a28150ad2821fa1e6dc4c017bf9

Tx prefix hash: 79b062f9d4fbaa9a6403e1218809dee2d6a11a80a0a9f306980743cc97d9a8fc
Tx public key: 3262b6c0353fb065b449e49f7aec1d3eb0aaa5936189cf3b77206f64e71ac079
Timestamp: 1709368860 Timestamp [UCT]: 2024-03-02 08:41:00 Age [y:d:h:m:s]: 00:267:18:48:00
Block: 969424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191709 RingCT/type: yes/0
Extra: 013262b6c0353fb065b449e49f7aec1d3eb0aaa5936189cf3b77206f64e71ac07902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1904eead9e43a3c2b0dd4d97313c9e97d3ad7298faaf611dd4ff73c5027e05ff 0.600000000000 1429253 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": 969434, "vin": [ { "gen": { "height": 969424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1904eead9e43a3c2b0dd4d97313c9e97d3ad7298faaf611dd4ff73c5027e05ff" } } ], "extra": [ 1, 50, 98, 182, 192, 53, 63, 176, 101, 180, 73, 228, 159, 122, 236, 29, 62, 176, 170, 165, 147, 97, 137, 207, 59, 119, 32, 111, 100, 231, 26, 192, 121, 2, 17, 0, 0, 0, 1, 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