Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9edeaa24f5b34e3a686014bcf3bf5f8e650ee68ef695c9ce3f9b08fd668fa4

Tx prefix hash: 5f385bccd85567ebf278d97eb435525a1d0249194909b05deaa387ad7136bb1d
Tx public key: 9fe52f9c916e289950dcd12b75b8ccbd64cbc45f046a203f4d0d14902a2a7d90
Timestamp: 1717296175 Timestamp [UCT]: 2024-06-02 02:42:55 Age [y:d:h:m:s]: 00:295:02:58:26
Block: 1035147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210901 RingCT/type: yes/0
Extra: 019fe52f9c916e289950dcd12b75b8ccbd64cbc45f046a203f4d0d14902a2a7d9002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 135b6aecd5e33d9fb78ae89685cfe46af4cae21654b396bd8b7a680d0270b254 0.600000000000 1503666 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": 1035157, "vin": [ { "gen": { "height": 1035147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135b6aecd5e33d9fb78ae89685cfe46af4cae21654b396bd8b7a680d0270b254" } } ], "extra": [ 1, 159, 229, 47, 156, 145, 110, 40, 153, 80, 220, 209, 43, 117, 184, 204, 189, 100, 203, 196, 95, 4, 106, 32, 63, 77, 13, 20, 144, 42, 42, 125, 144, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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