Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9cefff22e59982ba94ff1d15e86b1b4ac4d54d160b6058fe3afc2defe3ba19

Tx prefix hash: 7ad5552fbda495d72aae78aa507321ac35a4873f3de99e04f0e35324b5a32f6d
Tx public key: d6b8d35f260c6df344439ce5cda984923a84950177406ff6401b031cd5db22ca
Timestamp: 1617047737 Timestamp [UCT]: 2021-03-29 19:55:37 Age [y:d:h:m:s]: 03:346:02:14:48
Block: 229202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1006627 RingCT/type: yes/0
Extra: 01d6b8d35f260c6df344439ce5cda984923a84950177406ff6401b031cd5db22ca02110000007c912e63b8000000000000000000

1 output(s) for total of 106.800728671000 dcy

stealth address amount amount idx
00: 64cecd2fc5684a8764e22c793a099a734df8f73d6047302fd8ea35b05c63fc7a 106.800728671000 475536 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": 229212, "vin": [ { "gen": { "height": 229202 } } ], "vout": [ { "amount": 106800728671, "target": { "key": "64cecd2fc5684a8764e22c793a099a734df8f73d6047302fd8ea35b05c63fc7a" } } ], "extra": [ 1, 214, 184, 211, 95, 38, 12, 109, 243, 68, 67, 156, 229, 205, 169, 132, 146, 58, 132, 149, 1, 119, 64, 111, 246, 64, 27, 3, 28, 213, 219, 34, 202, 2, 17, 0, 0, 0, 124, 145, 46, 99, 184, 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