Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47b9bb3e984ed7fe4d782e9c4bb1eb3cb8acbec8c699d39b79b2be77dcdd3c53

Tx prefix hash: f988d74d9349acf8fa8e379d6cc0de40dd499df555a6553550ef2c6a8730fba3
Tx public key: fe75eec56d6d2bd277bc23e516c59829a862b985892ca8e10e9af13bf3895afc
Timestamp: 1786461471 Timestamp [UTC]: 2026-08-11 15:17:51 Age [y:d:h:m:s]: 00:102:18:47:52
Block: 1610999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 72495 RingCT/type: yes/0
Extra: 01fe75eec56d6d2bd277bc23e516c59829a862b985892ca8e10e9af13bf3895afc

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97f44648c13aaf8966306a98336386114e7bdd7ce7d9bea0561efdf89c0ade7e 0.000600000000 2101019 of 15 <44>

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": 1611009, "vin": [ { "gen": { "height": 1610999 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "97f44648c13aaf8966306a98336386114e7bdd7ce7d9bea0561efdf89c0ade7e", "view_tag": "44" } } } ], "extra": [ 1, 254, 117, 238, 197, 109, 109, 43, 210, 119, 188, 35, 229, 22, 197, 152, 41, 168, 98, 185, 133, 137, 44, 168, 225, 14, 154, 241, 59, 243, 137, 90, 252 ], "rct_signatures": { "type": 0 } }


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