Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0cc9fa1f76029bd63f9ca324ef023dbfa6550c60f56113cbd146ca918d74848

Tx prefix hash: 57c7581a08c1a73f922e43713bf60b75a64f17ebc6bea789db019bb742f11e2c
Tx public key: 2b473efa061967765bf3cf9c74e7ea2bf809563f33957ee3a674159eab9be671
Timestamp: 1753541471 Timestamp [UTC]: 2025-07-26 14:51:11 Age [y:d:h:m:s]: 01:117:05:04:44
Block: 1333858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349049 RingCT/type: yes/0
Extra: 012b473efa061967765bf3cf9c74e7ea2bf809563f33957ee3a674159eab9be671021100000001ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6a09a7288854d914f57b0ae7ea6c7d82eede06933cdfcdb2bf3e2f200f6cf0ca 0.000600000000 1821657 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": 1333868, "vin": [ { "gen": { "height": 1333858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a09a7288854d914f57b0ae7ea6c7d82eede06933cdfcdb2bf3e2f200f6cf0ca" } } ], "extra": [ 1, 43, 71, 62, 250, 6, 25, 103, 118, 91, 243, 207, 156, 116, 231, 234, 43, 248, 9, 86, 63, 51, 149, 126, 227, 166, 116, 21, 158, 171, 155, 230, 113, 2, 17, 0, 0, 0, 1, 239, 34, 20, 133, 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: