Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4761f7a432a0bab7c5fa22d5da2a92e62cc97db0ec4c2fe8ed4cf35daf0d01f3

Tx prefix hash: 7f2c18a07a722d38a8625ca5484ff926d1d4f364b73698c72d3ab392db2746bf
Tx public key: fb9f37f6b246e53dcb8dd5e58b959d26ad3b6e168bc6f57a200163d94a68c7ea
Timestamp: 1732942308 Timestamp [UCT]: 2024-11-30 04:51:48 Age [y:d:h:m:s]: 00:151:03:48:12
Block: 1164757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107875 RingCT/type: yes/0
Extra: 01fb9f37f6b246e53dcb8dd5e58b959d26ad3b6e168bc6f57a200163d94a68c7ea0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42aa6dfaa59647278e178c0d3f119214947a7e6abbaf64d6b800bbb4ab5a61fc 0.600000000000 1650432 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": 1164767, "vin": [ { "gen": { "height": 1164757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42aa6dfaa59647278e178c0d3f119214947a7e6abbaf64d6b800bbb4ab5a61fc" } } ], "extra": [ 1, 251, 159, 55, 246, 178, 70, 229, 61, 203, 141, 213, 229, 139, 149, 157, 38, 173, 59, 110, 22, 139, 198, 245, 122, 32, 1, 99, 217, 74, 104, 199, 234, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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