Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 389e9c5d3cc4b74a8addbf3b1cae7dfe5bd934d8a9dc80401d1e4fb43967dc0e

Tx prefix hash: 8e8064dc08e7c441f60b0f24566d6403dd419d6a19159318ab97cc417cefdc41
Tx public key: 3e6e9f85107b488fa25c0dbb3b5767098ac86b4997ef3fb2e8f5fad36ca4a046
Timestamp: 1791099538 Timestamp [UTC]: 2026-10-04 07:38:58 Age [y:d:h:m:s]: 00:038:07:01:28
Block: 1647913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 27999 RingCT/type: yes/0
Extra: 013e6e9f85107b488fa25c0dbb3b5767098ac86b4997ef3fb2e8f5fad36ca4a046

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 452d8837ae05d6dbc844f7f7ea8b12ab538edc3c81e1501cbc767ab9fed4d1c3 0.000600000000 2138069 of 15 <56>

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": 1647923, "vin": [ { "gen": { "height": 1647913 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "452d8837ae05d6dbc844f7f7ea8b12ab538edc3c81e1501cbc767ab9fed4d1c3", "view_tag": "56" } } } ], "extra": [ 1, 62, 110, 159, 133, 16, 123, 72, 143, 162, 92, 13, 187, 59, 87, 103, 9, 138, 200, 107, 73, 151, 239, 63, 178, 232, 245, 250, 211, 108, 164, 160, 70 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: