Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549eb30fb2adc8a158ffaa5f004693f9644f8d4121dab10dfd8b5c964740eca3

Tx prefix hash: 750c4f78c0aa242673fe17df14abbeb1e62452f8b0187753499ddcdc07feb024
Tx public key: 0af399840576a7c30f47a3c8de557850b6c16520b64cf86c8f480dd50561f2de
Timestamp: 1720508579 Timestamp [UTC]: 2024-07-09 07:02:59 Age [y:d:h:m:s]: 02:126:08:00:05
Block: 1061779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614932 RingCT/type: yes/0
Extra: 010af399840576a7c30f47a3c8de557850b6c16520b64cf86c8f480dd50561f2de021100000007e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a079968c769cbd42f4ab8d161462915300eb213e98e61b4e9ba09ad3e1530bc5 0.000600000000 1532274 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": 1061789, "vin": [ { "gen": { "height": 1061779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a079968c769cbd42f4ab8d161462915300eb213e98e61b4e9ba09ad3e1530bc5" } } ], "extra": [ 1, 10, 243, 153, 132, 5, 118, 167, 195, 15, 71, 163, 200, 222, 85, 120, 80, 182, 193, 101, 32, 182, 76, 248, 108, 143, 72, 13, 213, 5, 97, 242, 222, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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: