Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df0f75a3f17adf8ef23385434fe297a26f4ff2cd9cc11d3d5e0da359c490883c

Tx prefix hash: 48609000a8aac62a5c9e02486647691548cde7e2b51fd866809b0868fc02817b
Tx public key: 32b51eb19fc71228f83bbc600df86fcc259ea65a6d3eabbd19e014b236e1e835
Timestamp: 1761383304 Timestamp [UTC]: 2025-10-25 09:08:24 Age [y:d:h:m:s]: 01:027:07:57:36
Block: 1397538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285956 RingCT/type: yes/0
Extra: 0132b51eb19fc71228f83bbc600df86fcc259ea65a6d3eabbd19e014b236e1e835021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b8b286f82fb42903c0c207c42e97ddc0e7682f469ed4332f1e7f991e37d0f721 0.000600000000 1885829 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": 1397548, "vin": [ { "gen": { "height": 1397538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8b286f82fb42903c0c207c42e97ddc0e7682f469ed4332f1e7f991e37d0f721" } } ], "extra": [ 1, 50, 181, 30, 177, 159, 199, 18, 40, 248, 59, 188, 96, 13, 248, 111, 204, 37, 158, 166, 90, 109, 62, 171, 189, 25, 224, 20, 178, 54, 225, 232, 53, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: