Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43fc587ae7563f8af9a5ffd7c5072d573d28f5ced2fb610f1bfd519fc1fb98b

Tx prefix hash: 7244cc55aba3e85e04c3a022db117321cb6070d5c6aaf4e724039f8391ab277f
Tx public key: 745943a774703115f0e7414da85332605c523ae47047b1629d234033397f1279
Timestamp: 1743350150 Timestamp [UTC]: 2025-03-30 15:55:50 Age [y:d:h:m:s]: 01:229:16:43:59
Block: 1250641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428134 RingCT/type: yes/0
Extra: 01745943a774703115f0e7414da85332605c523ae47047b1629d234033397f12790211000000041a970403000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fff1fdfb99c70b0dd08503e8cdd03282f53bf6748fd9e645947ef7f2e25ff960 0.000600000000 1737692 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": 1250651, "vin": [ { "gen": { "height": 1250641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fff1fdfb99c70b0dd08503e8cdd03282f53bf6748fd9e645947ef7f2e25ff960" } } ], "extra": [ 1, 116, 89, 67, 167, 116, 112, 49, 21, 240, 231, 65, 77, 168, 83, 50, 96, 92, 82, 58, 228, 112, 71, 177, 98, 157, 35, 64, 51, 57, 127, 18, 121, 2, 17, 0, 0, 0, 4, 26, 151, 4, 3, 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: