Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 168f174c6bc95e226a68b7b6a26a959d0fbc2fddae59bfd4d316c4eb564234a2

Tx prefix hash: 7be4b12a37a0b30486b030a690ca26b1f4739e1e70386c6f57cab35f2f378c32
Tx public key: 1ee9d21a1b5a49cda0fda3e3da8aac6719bcb839cce8b5333d56f2088d4388c2
Timestamp: 1793725276 Timestamp [UTC]: 2026-11-03 17:01:16 Age [y:d:h:m:s]: 00:019:00:02:47
Block: 1669488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 14006 RingCT/type: yes/0
Extra: 011ee9d21a1b5a49cda0fda3e3da8aac6719bcb839cce8b5333d56f2088d4388c2

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 50de6f842639a7a5f0bcdaf3218efddcf2f1f73c524146cd88b7d3a9e27439cb 0.000600000000 2160246 of 15 <e8>

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": 1669498, "vin": [ { "gen": { "height": 1669488 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "50de6f842639a7a5f0bcdaf3218efddcf2f1f73c524146cd88b7d3a9e27439cb", "view_tag": "e8" } } } ], "extra": [ 1, 30, 233, 210, 26, 27, 90, 73, 205, 160, 253, 163, 227, 218, 138, 172, 103, 25, 188, 184, 57, 204, 232, 181, 51, 61, 86, 242, 8, 141, 67, 136, 194 ], "rct_signatures": { "type": 0 } }


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