Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ab5fe1fe5aec558c6dfd90b4faafb90a15b00606788a970322e875aafc3f82

Tx prefix hash: 70a8bc289d91967d385d56e3db0621bb7cc9748617c9baaccaa5d633a597f60a
Tx public key: 784856ee84fdcd238f775af7fecc271bd03f6720e5b58961bb1d61c341bff013
Timestamp: 1774770359 Timestamp [UTC]: 2026-03-29 07:45:59 Age [y:d:h:m:s]: 00:233:00:54:26
Block: 1508223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172043 RingCT/type: yes/0
Extra: 01784856ee84fdcd238f775af7fecc271bd03f6720e5b58961bb1d61c341bff013021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 850c71d592307fd2742e7c04402824f73b43c7b71bf641d530b0057710600e2a 0.000600000000 1997975 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 dinastycoin-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": 1508233, "vin": [ { "gen": { "height": 1508223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "850c71d592307fd2742e7c04402824f73b43c7b71bf641d530b0057710600e2a" } } ], "extra": [ 1, 120, 72, 86, 238, 132, 253, 205, 35, 143, 119, 90, 247, 254, 204, 39, 27, 208, 63, 103, 32, 229, 181, 137, 97, 187, 29, 97, 195, 65, 191, 240, 19, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: