Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ae824effedfcb7dc99063653c381d70419981b2a8a408e27048823fd89786dc

Tx prefix hash: ae7bdb9f3ce8e0d78786f478a87dddcdf257589a2b9bcc8d3520c24ff51ecf30
Tx public key: f04e279a68f735bbe3566511b3f6cc7de8e8fce1e566431e0882263e774d13f8
Timestamp: 1746728207 Timestamp [UTC]: 2025-05-08 18:16:47 Age [y:d:h:m:s]: 01:193:18:35:16
Block: 1278603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402537 RingCT/type: yes/0
Extra: 01f04e279a68f735bbe3566511b3f6cc7de8e8fce1e566431e0882263e774d13f80211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c196862947d2ebd73eedb524b64d993640695900eb79c46dcb5160930aba021c 0.000600000000 1765972 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": 1278613, "vin": [ { "gen": { "height": 1278603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c196862947d2ebd73eedb524b64d993640695900eb79c46dcb5160930aba021c" } } ], "extra": [ 1, 240, 78, 39, 154, 104, 247, 53, 187, 227, 86, 101, 17, 179, 246, 204, 125, 232, 232, 252, 225, 229, 102, 67, 30, 8, 130, 38, 62, 119, 77, 19, 248, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: