Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565795c8f633fa2d56a7a2de8545e5e47afc742a37025eb4ed4bcb7deb44e694

Tx prefix hash: a02e8307f3d242aa2a24525a4d18fc98c584d91c65850a3fa97c50f355c7909a
Tx public key: a5f7e027fc536be418201a8474c429dd98db356bf01633f7fbaba02d6c710940
Timestamp: 1747168980 Timestamp [UTC]: 2025-05-13 20:43:00 Age [y:d:h:m:s]: 01:066:09:51:25
Block: 1282272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300842 RingCT/type: yes/0
Extra: 01a5f7e027fc536be418201a8474c429dd98db356bf01633f7fbaba02d6c7109400211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6a713e5f49dc1c4077a10ee68583bd3f1301f41e48039cc2fcc3467f636d70ae 0.000600000000 1769679 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": 1282282, "vin": [ { "gen": { "height": 1282272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a713e5f49dc1c4077a10ee68583bd3f1301f41e48039cc2fcc3467f636d70ae" } } ], "extra": [ 1, 165, 247, 224, 39, 252, 83, 107, 228, 24, 32, 26, 132, 116, 196, 41, 221, 152, 219, 53, 107, 240, 22, 51, 247, 251, 171, 160, 45, 108, 113, 9, 64, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: