Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4fbd2bf66259ca5b10579023618d8c5b23e58f323adcd723cf62c8d0f71b976

Tx prefix hash: 433e2797248e27054319e439b19eb6de0c9075781d075f391d8a8d2e1770e6ac
Tx public key: 596d63538794534be4517c9146d99d2ba830361978b1a74819a8f1cea156ecd0
Timestamp: 1764874820 Timestamp [UTC]: 2025-12-04 19:00:20 Age [y:d:h:m:s]: 00:345:11:47:02
Block: 1426466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252246 RingCT/type: yes/0
Extra: 01596d63538794534be4517c9146d99d2ba830361978b1a74819a8f1cea156ecd0021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c18a1d2a14229c07e3e4f650ecffdc937317c7dd6902a377792b28c27e6731e7 0.000600000000 1915157 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": 1426476, "vin": [ { "gen": { "height": 1426466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c18a1d2a14229c07e3e4f650ecffdc937317c7dd6902a377792b28c27e6731e7" } } ], "extra": [ 1, 89, 109, 99, 83, 135, 148, 83, 75, 228, 81, 124, 145, 70, 217, 157, 43, 168, 48, 54, 25, 120, 177, 167, 72, 25, 168, 241, 206, 161, 86, 236, 208, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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: