Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eefdd95d666c18b1615e5e80cd7629c5b3c28669b0f71bb8d35c0f5fbed4e7cb

Tx prefix hash: 59138f57fb74caee43efae4aea4d85117d4db88361940f5d5d5874b81d439c7d
Tx public key: 5ea8883435b364baa34b80730e0382bf60e447165b16e8f608db0a9ccf64d54d
Timestamp: 1772123862 Timestamp [UTC]: 2026-02-26 16:37:42 Age [y:d:h:m:s]: 00:260:15:28:21
Block: 1486316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191682 RingCT/type: yes/0
Extra: 015ea8883435b364baa34b80730e0382bf60e447165b16e8f608db0a9ccf64d54d021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fc1f51092d12d9d835424f24c669c8c9a549e72c0cf45311f3be7ce6632e6d15 0.000600000000 1975766 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": 1486326, "vin": [ { "gen": { "height": 1486316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc1f51092d12d9d835424f24c669c8c9a549e72c0cf45311f3be7ce6632e6d15" } } ], "extra": [ 1, 94, 168, 136, 52, 53, 179, 100, 186, 163, 75, 128, 115, 14, 3, 130, 191, 96, 228, 71, 22, 91, 22, 232, 246, 8, 219, 10, 156, 207, 100, 213, 77, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: