Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82be60289dc7cc351fbedb325c86624c125e62c687e20c3bc4792e29e7ed332e

Tx prefix hash: 422ec289ae1de3a9a09278d5b45e4a6c252280c6087f3736e81ecefa54db156f
Tx public key: b46ab28f03d4b37d83ad55a036596bb7b683a23a89447e37da6f2d68ccec770c
Timestamp: 1745331145 Timestamp [UTC]: 2025-04-22 14:12:25 Age [y:d:h:m:s]: 01:208:16:04:57
Block: 1267048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413144 RingCT/type: yes/0
Extra: 01b46ab28f03d4b37d83ad55a036596bb7b683a23a89447e37da6f2d68ccec770c02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c30a64394e6efee014a4d772aef1242c66b609eb1e3bd7d2bc0ab6c5b438b3af 0.000600000000 1754273 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": 1267058, "vin": [ { "gen": { "height": 1267048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c30a64394e6efee014a4d772aef1242c66b609eb1e3bd7d2bc0ab6c5b438b3af" } } ], "extra": [ 1, 180, 106, 178, 143, 3, 212, 179, 125, 131, 173, 85, 160, 54, 89, 107, 183, 182, 131, 162, 58, 137, 68, 126, 55, 218, 111, 45, 104, 204, 236, 119, 12, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: