Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a330c354fec758c54d48931f68c4637830c5253d3c0b969dfca1d4a4785c4e79

Tx prefix hash: 23ff96d84548985eb345c9599f5111249c28ef7cdfa40bcace8d3ff95c938c80
Tx public key: 0fe8ec33698b91229095e8af4b5067d45198ce410593b47f66b9384c3d86d099
Timestamp: 1770248512 Timestamp [UTC]: 2026-02-04 23:41:52 Age [y:d:h:m:s]: 00:282:01:50:47
Block: 1470831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206965 RingCT/type: yes/0
Extra: 010fe8ec33698b91229095e8af4b5067d45198ce410593b47f66b9384c3d86d099021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65ee885139d70558f88b19e13b876c76588e311b0eedd4899b8a096e0e3b6c06 0.000600000000 1960101 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": 1470841, "vin": [ { "gen": { "height": 1470831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65ee885139d70558f88b19e13b876c76588e311b0eedd4899b8a096e0e3b6c06" } } ], "extra": [ 1, 15, 232, 236, 51, 105, 139, 145, 34, 144, 149, 232, 175, 75, 80, 103, 212, 81, 152, 206, 65, 5, 147, 180, 127, 102, 185, 56, 76, 61, 134, 208, 153, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: