Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aaf631b01b6e556b4137f793cc36997817a60c0c92c5b396ac501cc2a52e97a

Tx prefix hash: ae383a2fd354b85e98d6553d3a081a92e7d16d463d59a88676e4178b9cc95850
Tx public key: 40e66a7998ad48085e19ebc4215aa24ce59d472b07fe1ba67693af6c68727e28
Timestamp: 1733104576 Timestamp [UCT]: 2024-12-02 01:56:16 Age [y:d:h:m:s]: 00:108:11:36:24
Block: 1166095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77362 RingCT/type: yes/0
Extra: 0140e66a7998ad48085e19ebc4215aa24ce59d472b07fe1ba67693af6c68727e28021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19b4d8b5796c1655c2ca94c6dc24cf9a4ae99ca15d41ec3c269e987a7d4a6eae 0.600000000000 1651772 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": 1166105, "vin": [ { "gen": { "height": 1166095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19b4d8b5796c1655c2ca94c6dc24cf9a4ae99ca15d41ec3c269e987a7d4a6eae" } } ], "extra": [ 1, 64, 230, 106, 121, 152, 173, 72, 8, 94, 25, 235, 196, 33, 90, 162, 76, 229, 157, 71, 43, 7, 254, 27, 166, 118, 147, 175, 108, 104, 114, 126, 40, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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