Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832dcb3be52468ae6f4e35432b9cb2ac11e2aadf5eeea7f55b97a57d6e23694e

Tx prefix hash: f52dc1f322146d177a0d19b1ba7fa126d98459b381fd3c96466c665d783cfcf6
Tx public key: e3a8cf38a81e87beff5a8bd1d3900ec612550912d4cc0d1937e242617807e5b3
Timestamp: 1706985839 Timestamp [UCT]: 2024-02-03 18:43:59 Age [y:d:h:m:s]: 01:093:08:48:17
Block: 949643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327815 RingCT/type: yes/0
Extra: 01e3a8cf38a81e87beff5a8bd1d3900ec612550912d4cc0d1937e242617807e5b302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1b40a96adbd0afcd57707654beba124b6c078d5f6a1fa73419faca90ed840cc 0.600000000000 1408173 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": 949653, "vin": [ { "gen": { "height": 949643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1b40a96adbd0afcd57707654beba124b6c078d5f6a1fa73419faca90ed840cc" } } ], "extra": [ 1, 227, 168, 207, 56, 168, 30, 135, 190, 255, 90, 139, 209, 211, 144, 14, 198, 18, 85, 9, 18, 212, 204, 13, 25, 55, 226, 66, 97, 120, 7, 229, 179, 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