Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 472d33b3047b5cc7441ec6a8032102d041d3c73a6b3387ad742ccd25bcaad00e

Tx prefix hash: c054f4fcb1bf91f4e9498534be0c78a95a7aa83516ce2656e48ae3276c2b39da
Tx public key: af7e560798cd325827024c817ec68fb1fac88483f6c13b1526866c1dc36b6b02
Timestamp: 1757452048 Timestamp [UTC]: 2025-09-09 21:07:28 Age [y:d:h:m:s]: 00:251:15:06:45
Block: 1364972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173277 RingCT/type: yes/0
Extra: 01af7e560798cd325827024c817ec68fb1fac88483f6c13b1526866c1dc36b6b02021100000007ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7d11ba79bde47012f4d029df7d731f667ba0727aa6ef1e03459e7321546d2448 0.000600000000 1853011 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": 1364982, "vin": [ { "gen": { "height": 1364972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d11ba79bde47012f4d029df7d731f667ba0727aa6ef1e03459e7321546d2448" } } ], "extra": [ 1, 175, 126, 86, 7, 152, 205, 50, 88, 39, 2, 76, 129, 126, 198, 143, 177, 250, 200, 132, 131, 246, 193, 59, 21, 38, 134, 108, 29, 195, 107, 107, 2, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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: