Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb2dd3b636a6df92669fbe566f1ec59f8e3a2b3178934026e22b870cea4332cc

Tx prefix hash: f042dbeb485fabece387fe3acb930fc114c300354b47d263d24aed7d0dee3b1f
Tx public key: 7199e51b97e5690c68eb94614821f5bd2e28299740fce83f83230ce855f453a1
Timestamp: 1784105232 Timestamp [UTC]: 2026-07-15 08:47:12 Age [y:d:h:m:s]: 00:126:09:31:44
Block: 1582773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98535 RingCT/type: yes/0
Extra: 017199e51b97e5690c68eb94614821f5bd2e28299740fce83f83230ce855f453a10208ba4a2211283808bc

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe7b7ba9d89ac0fa0dc3a60395def5823cb4241bbc4aa5a02abd403809c1ef74 0.000600000000 2072767 of 15 <a7>

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": 1582783, "vin": [ { "gen": { "height": 1582773 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "fe7b7ba9d89ac0fa0dc3a60395def5823cb4241bbc4aa5a02abd403809c1ef74", "view_tag": "a7" } } } ], "extra": [ 1, 113, 153, 229, 27, 151, 229, 105, 12, 104, 235, 148, 97, 72, 33, 245, 189, 46, 40, 41, 151, 64, 252, 232, 63, 131, 35, 12, 232, 85, 244, 83, 161, 2, 8, 186, 74, 34, 17, 40, 56, 8, 188 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: