Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f94a1cbfbec1e7ed4a10de33e95a54aecc3efe7d0b342f5a831dabeae47fb790

Tx prefix hash: a4290aba4dbf1388a558c216aed675f79a4be7b83f8c9ccf85b7f40c346581ab
Tx public key: a9d245c750a4cde59a62570b395febf9944e5e6dfa0c3ca062972fbbfc653a0c
Timestamp: 1753600981 Timestamp [UTC]: 2025-07-27 07:23:01 Age [y:d:h:m:s]: 01:112:15:50:14
Block: 1334349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345639 RingCT/type: yes/0
Extra: 01a9d245c750a4cde59a62570b395febf9944e5e6dfa0c3ca062972fbbfc653a0c021100000005ef221485000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a5df7b806855b7f84666225cda08491d8a746d71595166b607b98cee16e76fff 0.000600000000 1822150 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": 1334359, "vin": [ { "gen": { "height": 1334349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5df7b806855b7f84666225cda08491d8a746d71595166b607b98cee16e76fff" } } ], "extra": [ 1, 169, 210, 69, 199, 80, 164, 205, 229, 154, 98, 87, 11, 57, 95, 235, 249, 148, 78, 94, 109, 250, 12, 60, 160, 98, 151, 47, 187, 252, 101, 58, 12, 2, 17, 0, 0, 0, 5, 239, 34, 20, 133, 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: