Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f092d7554bd788bb2541551956e6a803c4e92d9625d2909d0a2251c1964e6285

Tx prefix hash: 02e424b799404e8383c79f35bd6951918873bac38074d4c8807f6d75464b303a
Tx public key: d9c1e8ec9749521a2804eda8a8042b87170f014ad4313f818951c092bdc23b8d
Timestamp: 1695640365 Timestamp [UCT]: 2023-09-25 11:12:45 Age [y:d:h:m:s]: 01:109:07:32:06
Block: 855798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339410 RingCT/type: yes/0
Extra: 01d9c1e8ec9749521a2804eda8a8042b87170f014ad4313f818951c092bdc23b8d02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.896160950000 dcy

stealth address amount amount idx
00: f6ec185cde838258f0d18a97067ff55fb5b3a7210e1cb34bf20ac5d2de049c3e 0.896160950000 1309842 of 0

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": 855808, "vin": [ { "gen": { "height": 855798 } } ], "vout": [ { "amount": 896160950, "target": { "key": "f6ec185cde838258f0d18a97067ff55fb5b3a7210e1cb34bf20ac5d2de049c3e" } } ], "extra": [ 1, 217, 193, 232, 236, 151, 73, 82, 26, 40, 4, 237, 168, 168, 4, 43, 135, 23, 15, 1, 74, 212, 49, 63, 129, 137, 81, 192, 146, 189, 194, 59, 141, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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