Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c20fe3ef6ebe101435095adb7b37a7a988a1ca41fe1cdc42fb9d85d5b9dd91

Tx prefix hash: 07c6a7df5fbac79647baf89e9d915bea9a86ad18893f65369e6903574a2c0e79
Tx public key: 889bef36870617bf44b5728c554b2518e9d850c6280e0f513d58f50222c81493
Timestamp: 1772067031 Timestamp [UTC]: 2026-02-26 00:50:31 Age [y:d:h:m:s]: 00:266:08:42:08
Block: 1485894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195897 RingCT/type: yes/0
Extra: 01889bef36870617bf44b5728c554b2518e9d850c6280e0f513d58f50222c81493021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d4e38021254d18334f25423004c9d689f66512c9211f3467c3ba388f214fa46f 0.000600000000 1975334 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": 1485904, "vin": [ { "gen": { "height": 1485894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4e38021254d18334f25423004c9d689f66512c9211f3467c3ba388f214fa46f" } } ], "extra": [ 1, 136, 155, 239, 54, 135, 6, 23, 191, 68, 181, 114, 140, 85, 75, 37, 24, 233, 216, 80, 198, 40, 14, 15, 81, 61, 88, 245, 2, 34, 200, 20, 147, 2, 17, 0, 0, 0, 9, 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: