Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51234215e5deee65da1c4c5a9a86fdbb3f619cc3f984ef4b3447ba3aaca27ded

Tx prefix hash: 2b81ab672095c49e8f5beffd919167f78d97d57bef631d26b3e770a26f17951f
Tx public key: 25f5645d74f08d25db7be88e10c6ffb3b45428ca4fce4ffa8254728aca2f3ca7
Timestamp: 1772132441 Timestamp [UTC]: 2026-02-26 19:00:41 Age [y:d:h:m:s]: 00:266:23:14:11
Block: 1486383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196476 RingCT/type: yes/0
Extra: 0125f5645d74f08d25db7be88e10c6ffb3b45428ca4fce4ffa8254728aca2f3ca7021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 72af753f7b05f5b85c9c0eb3f18ad424ca165ffecca53a9e8ee2008c7d32dd19 0.000600000000 1975837 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": 1486393, "vin": [ { "gen": { "height": 1486383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72af753f7b05f5b85c9c0eb3f18ad424ca165ffecca53a9e8ee2008c7d32dd19" } } ], "extra": [ 1, 37, 245, 100, 93, 116, 240, 141, 37, 219, 123, 232, 142, 16, 198, 255, 179, 180, 84, 40, 202, 79, 206, 79, 250, 130, 84, 114, 138, 202, 47, 60, 167, 2, 17, 0, 0, 0, 1, 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: