Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ea0cd075553cb23744a8a582e6d7cdd618be38543283e2b196036ec6f7155ef

Tx prefix hash: 27cc584da55229a342cb97f7e48c165fe43db28de6990d44c48d8f7d371e347a
Tx public key: d13c1da0a93da5b026675386d7e4839e23271b8ec9171a9ad2de77333099d011
Timestamp: 1771684772 Timestamp [UTC]: 2026-02-21 14:39:32 Age [y:d:h:m:s]: 00:270:15:16:50
Block: 1482697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198985 RingCT/type: yes/0
Extra: 01d13c1da0a93da5b026675386d7e4839e23271b8ec9171a9ad2de77333099d011021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80c4ef87b32adc1f8afdcf7823b8d2237f17cad296d528eb4bfc92332ebc6b25 0.000600000000 1972091 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": 1482707, "vin": [ { "gen": { "height": 1482697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80c4ef87b32adc1f8afdcf7823b8d2237f17cad296d528eb4bfc92332ebc6b25" } } ], "extra": [ 1, 209, 60, 29, 160, 169, 61, 165, 176, 38, 103, 83, 134, 215, 228, 131, 158, 35, 39, 27, 142, 201, 23, 26, 154, 210, 222, 119, 51, 48, 153, 208, 17, 2, 17, 0, 0, 0, 2, 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: