Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6dab93b3e798e11ed631380edd77b0cc0b60fb8caff3b2e980dabd78a24f7a

Tx prefix hash: a76cde5f9922214a68bbd3e481055961483b1aa769b899daaa037367c47ab65b
Tx public key: 3703bb13960aad68e118dfebb9d4d948b2960f9417d45f4683891d79d1a0346d
Timestamp: 1772183636 Timestamp [UTC]: 2026-02-27 09:13:56 Age [y:d:h:m:s]: 00:266:17:26:07
Block: 1486804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196301 RingCT/type: yes/0
Extra: 013703bb13960aad68e118dfebb9d4d948b2960f9417d45f4683891d79d1a0346d021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08fe548035b057df0d5d25fa3f69ce7888f1926ca7d1826d36dfd09476b25d2b 0.000600000000 1976262 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": 1486814, "vin": [ { "gen": { "height": 1486804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08fe548035b057df0d5d25fa3f69ce7888f1926ca7d1826d36dfd09476b25d2b" } } ], "extra": [ 1, 55, 3, 187, 19, 150, 10, 173, 104, 225, 24, 223, 235, 185, 212, 217, 72, 178, 150, 15, 148, 23, 212, 95, 70, 131, 137, 29, 121, 209, 160, 52, 109, 2, 17, 0, 0, 0, 4, 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: