Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecfd066a35b95b9fcbc74c90c620f460304992d4332eabd840fe09fbbe7f4950

Tx prefix hash: 2595bf5253e12119a70ed3b0e55b37bc10646b2702a299a0eccc4c536f9598b0
Tx public key: e5990dd00a18f60d8b4b5a40770eee0e2263cb394bc7544fda666c2a75b4cef8
Timestamp: 1771940706 Timestamp [UTC]: 2026-02-24 13:45:06 Age [y:d:h:m:s]: 00:268:12:53:45
Block: 1484825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197515 RingCT/type: yes/0
Extra: 01e5990dd00a18f60d8b4b5a40770eee0e2263cb394bc7544fda666c2a75b4cef8021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9860127369dde25d72b81eb3914236dee55c4947e7192006ec53787b5c1cbceb 0.000600000000 1974255 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": 1484835, "vin": [ { "gen": { "height": 1484825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9860127369dde25d72b81eb3914236dee55c4947e7192006ec53787b5c1cbceb" } } ], "extra": [ 1, 229, 153, 13, 208, 10, 24, 246, 13, 139, 75, 90, 64, 119, 14, 238, 14, 34, 99, 203, 57, 75, 199, 84, 79, 218, 102, 108, 42, 117, 180, 206, 248, 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: