Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef4ac62dbcba7497b5481803b1e91a8b3eec9e0c168431a94274cbcd5b0b86c4

Tx prefix hash: f99049eca8ec9fed37c3c4172661e91d1d3768d9de7bc1c245e3ecc680338386
Tx public key: fa6a331cd2f794c974302b4085a3670784ac67b73d122af17cdc6f142e41807e
Timestamp: 1771279814 Timestamp [UTC]: 2026-02-16 22:10:14 Age [y:d:h:m:s]: 00:090:22:18:32
Block: 1479328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57602 RingCT/type: yes/0
Extra: 01fa6a331cd2f794c974302b4085a3670784ac67b73d122af17cdc6f142e41807e021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 433629ba5c17d6e813b7377bd683885976f876ec0be748821bafca7239cb7d3f 0.000600000000 1968672 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": 1479338, "vin": [ { "gen": { "height": 1479328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "433629ba5c17d6e813b7377bd683885976f876ec0be748821bafca7239cb7d3f" } } ], "extra": [ 1, 250, 106, 51, 28, 210, 247, 148, 201, 116, 48, 43, 64, 133, 163, 103, 7, 132, 172, 103, 183, 61, 18, 42, 241, 124, 220, 111, 20, 46, 65, 128, 126, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: