Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa4661b589d7d323fbb33b2bc4c64cf258a63e2cfb53d156133e2d4c23bcaf8

Tx prefix hash: 02eb99578606780d85642f3a5a2fbb1cc7e3522bbbd2a9d22516cd31fb84946e
Tx public key: 40a557fce8f8a6f8120d29f0775c92c00bd093554ff0609fe61fef373eceb294
Timestamp: 1742647006 Timestamp [UTC]: 2025-03-22 12:36:46 Age [y:d:h:m:s]: 01:128:13:01:42
Block: 1244835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355845 RingCT/type: yes/0
Extra: 0140a557fce8f8a6f8120d29f0775c92c00bd093554ff0609fe61fef373eceb294021100000004ca0c97f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 655f58ca96a115d5f7d90267be64e1a4ee37af1a919b27a8cd34be755aba2ab0 0.000600000000 1731826 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": 1244845, "vin": [ { "gen": { "height": 1244835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "655f58ca96a115d5f7d90267be64e1a4ee37af1a919b27a8cd34be755aba2ab0" } } ], "extra": [ 1, 64, 165, 87, 252, 232, 248, 166, 248, 18, 13, 41, 240, 119, 92, 146, 192, 11, 208, 147, 85, 79, 240, 96, 159, 230, 31, 239, 55, 62, 206, 178, 148, 2, 17, 0, 0, 0, 4, 202, 12, 151, 245, 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: