Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a8b8371d4323644a64a7258785f7d0f27f66e432d79c971af5fc30832f87d4

Tx prefix hash: e33cb9112ae5a1ff590215c5da624dbc812c5d8144bef946ea855e33569bd5d1
Tx public key: 8fef4c1ebe71a27a732c075a684baa342dce60fa0ef998fddd94fab8dc7cf7df
Timestamp: 1772210302 Timestamp [UTC]: 2026-02-27 16:38:22 Age [y:d:h:m:s]: 00:266:13:08:16
Block: 1487040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196164 RingCT/type: yes/0
Extra: 018fef4c1ebe71a27a732c075a684baa342dce60fa0ef998fddd94fab8dc7cf7df021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 06329e2607fcf35be4cf8f6f45ca061975c95416d1369d591570a477a56a023c 0.000600000000 1976502 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": 1487050, "vin": [ { "gen": { "height": 1487040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06329e2607fcf35be4cf8f6f45ca061975c95416d1369d591570a477a56a023c" } } ], "extra": [ 1, 143, 239, 76, 30, 190, 113, 162, 122, 115, 44, 7, 90, 104, 75, 170, 52, 45, 206, 96, 250, 14, 249, 152, 253, 221, 148, 250, 184, 220, 124, 247, 223, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: