Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 463087269b1e5830d7d84b19d7df5c450e10a7acf0d25dc1dc0efed29f15d4e3

Tx prefix hash: 20640148c5a70455206eeb5ea033a5ae0cce7d345c30886b9213017681efdaed
Tx public key: 08531dfeabd0eeb245a8604e6168e75a616c61af14229813ec0cdf8f6747f21d
Timestamp: 1746245005 Timestamp [UTC]: 2025-05-03 04:03:25 Age [y:d:h:m:s]: 01:197:22:40:57
Block: 1274609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405480 RingCT/type: yes/0
Extra: 0108531dfeabd0eeb245a8604e6168e75a616c61af14229813ec0cdf8f6747f21d02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e66f9fea34cd2f0a15d2bfa6fec6c3980a4fb96b940056ec53b21c6c8c3d8800 0.000600000000 1761904 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": 1274619, "vin": [ { "gen": { "height": 1274609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66f9fea34cd2f0a15d2bfa6fec6c3980a4fb96b940056ec53b21c6c8c3d8800" } } ], "extra": [ 1, 8, 83, 29, 254, 171, 208, 238, 178, 69, 168, 96, 78, 97, 104, 231, 90, 97, 108, 97, 175, 20, 34, 152, 19, 236, 12, 223, 143, 103, 71, 242, 29, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: