Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c635c94dd48941ae3c3d2cbd21c0054c52f7f62c9c021c739344afa48d63b244

Tx prefix hash: ac9c9d85e4121ca6e1ca540e17968b55b4a54359be5df6a85baa4792d75181da
Tx public key: 2fee6e8acf714500ed9a6580f27c78eddd95b953d311127ae4d4bd993d366f20
Timestamp: 1730957066 Timestamp [UCT]: 2024-11-07 05:24:26 Age [y:d:h:m:s]: 00:017:02:26:53
Block: 1148310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12239 RingCT/type: yes/0
Extra: 012fee6e8acf714500ed9a6580f27c78eddd95b953d311127ae4d4bd993d366f200211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa08545b98fe6b010c0d115da455cceb1eda04d8791ce020c5235f8b144f085 0.600000000000 1633123 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": 1148320, "vin": [ { "gen": { "height": 1148310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa08545b98fe6b010c0d115da455cceb1eda04d8791ce020c5235f8b144f085" } } ], "extra": [ 1, 47, 238, 110, 138, 207, 113, 69, 0, 237, 154, 101, 128, 242, 124, 120, 237, 221, 149, 185, 83, 211, 17, 18, 122, 228, 212, 189, 153, 61, 54, 111, 32, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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