Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2efca0d3ee276201246cb57b7b17efae42a04f9ef7950199a2c7dd7fa61e75aa

Tx prefix hash: 33e1d429366bd8d31eebbb4d1b8e0e7452df72427b697e618b476d1609767736
Tx public key: 065977e001367e6f0223f91269ab5cf8902359251f4e3037fec8dff359359cd4
Timestamp: 1769639854 Timestamp [UTC]: 2026-01-28 22:37:34 Age [y:d:h:m:s]: 00:281:09:04:26
Block: 1465768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205864 RingCT/type: yes/0
Extra: 01065977e001367e6f0223f91269ab5cf8902359251f4e3037fec8dff359359cd4021100000004215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f9515c6ac0e2b6d6c57d73ec07c3549a3e17283d3186db82b25e03422aa4bc0 0.000600000000 1954998 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": 1465778, "vin": [ { "gen": { "height": 1465768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f9515c6ac0e2b6d6c57d73ec07c3549a3e17283d3186db82b25e03422aa4bc0" } } ], "extra": [ 1, 6, 89, 119, 224, 1, 54, 126, 111, 2, 35, 249, 18, 105, 171, 92, 248, 144, 35, 89, 37, 31, 78, 48, 55, 254, 200, 223, 243, 89, 53, 156, 212, 2, 17, 0, 0, 0, 4, 33, 91, 191, 137, 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: