Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06aa4cfd1bf2f1f8e8d5003caa0fd036e558eab3752134109eabedf59b953937

Tx prefix hash: 11532b2b1d397ef06fac2c49a849e482f0f9ae1c74d3de6480fe03b4a9b1d309
Tx public key: 7fce772307a34d5d8880aa0fc3569b4150e39b6ef8d6a8fa9ac3830ea944eaea
Timestamp: 1775112308 Timestamp [UTC]: 2026-04-02 06:45:08 Age [y:d:h:m:s]: 00:225:23:07:19
Block: 1511051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166882 RingCT/type: yes/0
Extra: 017fce772307a34d5d8880aa0fc3569b4150e39b6ef8d6a8fa9ac3830ea944eaea021100000003ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0168f9898231de9369d4148a14bf59fe4019feae80b7fd3646b593684e748cd9 0.000600000000 2000839 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": 1511061, "vin": [ { "gen": { "height": 1511051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0168f9898231de9369d4148a14bf59fe4019feae80b7fd3646b593684e748cd9" } } ], "extra": [ 1, 127, 206, 119, 35, 7, 163, 77, 93, 136, 128, 170, 15, 195, 86, 155, 65, 80, 227, 155, 110, 248, 214, 168, 250, 154, 195, 131, 14, 169, 68, 234, 234, 2, 17, 0, 0, 0, 3, 238, 75, 113, 129, 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: