Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243d4040ecc299726abe9486f1c43da1e45530ae82eccef54ae43b2e6780dc0c

Tx prefix hash: bf62a89bd726d153bcd6517835369e74e97cb16eecb2c38d9c91aae03434c7b5
Tx public key: f4373082402ef1574aecf2acabd93c3415ab1a20388e47da37d903c0acb67fa6
Timestamp: 1771764512 Timestamp [UTC]: 2026-02-22 12:48:32 Age [y:d:h:m:s]: 00:269:20:14:02
Block: 1483357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198417 RingCT/type: yes/0
Extra: 01f4373082402ef1574aecf2acabd93c3415ab1a20388e47da37d903c0acb67fa6021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a71c18d15911197b42110a3f3475fc890b8c0639bbf076bb7df19944fdea1794 0.000600000000 1972763 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": 1483367, "vin": [ { "gen": { "height": 1483357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71c18d15911197b42110a3f3475fc890b8c0639bbf076bb7df19944fdea1794" } } ], "extra": [ 1, 244, 55, 48, 130, 64, 46, 241, 87, 74, 236, 242, 172, 171, 217, 60, 52, 21, 171, 26, 32, 56, 142, 71, 218, 55, 217, 3, 192, 172, 182, 127, 166, 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: