Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495159e6da79400964ba19d5aaeb3067f7e85d316909e40475fb9f761f0e796e

Tx prefix hash: 949878c1c4142ec6b67f51205a9b65a64fffc70dab2245fc1dff58116aaa7385
Tx public key: ff61d0df8df2d66da3620b8523d2f42a77131e9bd6d021e531a9c47fd03110b7
Timestamp: 1764829922 Timestamp [UTC]: 2025-12-04 06:32:02 Age [y:d:h:m:s]: 00:157:15:00:00
Block: 1426087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105276 RingCT/type: yes/0
Extra: 01ff61d0df8df2d66da3620b8523d2f42a77131e9bd6d021e531a9c47fd03110b7021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a862dac80ec1ad2d7d9bf04c1f3be4da903e33568b01cb7bf393ee745f18099 0.000600000000 1914770 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": 1426097, "vin": [ { "gen": { "height": 1426087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a862dac80ec1ad2d7d9bf04c1f3be4da903e33568b01cb7bf393ee745f18099" } } ], "extra": [ 1, 255, 97, 208, 223, 141, 242, 214, 109, 163, 98, 11, 133, 35, 210, 244, 42, 119, 19, 30, 155, 214, 208, 33, 229, 49, 169, 196, 127, 208, 49, 16, 183, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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: