Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68cf0fa997be8bc47642413f3f60b1b05fbfaeeed33df0c9adaed62c139519ea

Tx prefix hash: e7f63b625f6c5c8679151b51c910033fc2e0cd64b698ef3e3644122b4e92dc92
Tx public key: df275279f6ea51106edf6a5b5f9723c8a536e81166cb76b926d37832a3a96620
Timestamp: 1772182741 Timestamp [UTC]: 2026-02-27 08:59:01 Age [y:d:h:m:s]: 00:266:18:18:21
Block: 1486798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196329 RingCT/type: yes/0
Extra: 01df275279f6ea51106edf6a5b5f9723c8a536e81166cb76b926d37832a3a96620021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4773844eb9807b42d454bf3c44c76ab6e5058ca4f69aa11b10d4ef184edfd8c 0.000600000000 1976256 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": 1486808, "vin": [ { "gen": { "height": 1486798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4773844eb9807b42d454bf3c44c76ab6e5058ca4f69aa11b10d4ef184edfd8c" } } ], "extra": [ 1, 223, 39, 82, 121, 246, 234, 81, 16, 110, 223, 106, 91, 95, 151, 35, 200, 165, 54, 232, 17, 102, 203, 118, 185, 38, 211, 120, 50, 163, 169, 102, 32, 2, 17, 0, 0, 0, 4, 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: