Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69040a7d57f068c54d532b5e79cd25dcbfcfed1686d4619dfc3561a30c6ea667

Tx prefix hash: 845b906e66ec38d3b0268b9616e9756cfbabd16b42af5f51c4a48148be6db51b
Tx public key: ea67c1fdfc4f3454823da0f23e83c5466228de667254838943a3a2e549564c0f
Timestamp: 1772190918 Timestamp [UTC]: 2026-02-27 11:15:18 Age [y:d:h:m:s]: 00:266:16:55:24
Block: 1486872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196281 RingCT/type: yes/0
Extra: 01ea67c1fdfc4f3454823da0f23e83c5466228de667254838943a3a2e549564c0f021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cadbf717441b8b118db81a15fc41206e34773239ee3ce3520d4e1b2b5bbe3c62 0.000600000000 1976330 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": 1486882, "vin": [ { "gen": { "height": 1486872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cadbf717441b8b118db81a15fc41206e34773239ee3ce3520d4e1b2b5bbe3c62" } } ], "extra": [ 1, 234, 103, 193, 253, 252, 79, 52, 84, 130, 61, 160, 242, 62, 131, 197, 70, 98, 40, 222, 102, 114, 84, 131, 137, 67, 163, 162, 229, 73, 86, 76, 15, 2, 17, 0, 0, 0, 6, 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: