Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a93aae92c4e32288069f658a19e7a49f4fa57ca4621661c972cbfa020dd08ba

Tx prefix hash: bc7e8e6b767e1bb64d85e1287ed19db35fa08d46b3a3ae993a6ffbfbc86c2266
Tx public key: a03fc1facf3009ba0221df07a305f9f2b88cad5d04f80d5cfbd3fdf1c47af8e2
Timestamp: 1745611266 Timestamp [UTC]: 2025-04-25 20:01:06 Age [y:d:h:m:s]: 01:206:14:05:01
Block: 1269374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411680 RingCT/type: yes/0
Extra: 01a03fc1facf3009ba0221df07a305f9f2b88cad5d04f80d5cfbd3fdf1c47af8e20211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a6758d773c54240fc0850ee257d0d87ceb816eb7e8827241330f7b92c35f394f 0.000600000000 1756609 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": 1269384, "vin": [ { "gen": { "height": 1269374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6758d773c54240fc0850ee257d0d87ceb816eb7e8827241330f7b92c35f394f" } } ], "extra": [ 1, 160, 63, 193, 250, 207, 48, 9, 186, 2, 33, 223, 7, 163, 5, 249, 242, 184, 140, 173, 93, 4, 248, 13, 92, 251, 211, 253, 241, 196, 122, 248, 226, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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: