Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2739da646fcb76a8f490c8ba6ee1f683d87c5c4ca3c89583a209db89e9b16bc

Tx prefix hash: 93b59083bee73a72ec49faa9fabf8e3902b5060a65658c5b0157e571cb0049dd
Tx public key: 3fefe6d7a8ed74dbbfc33b49d227357cb7e64349039710701e4bc2222400e3ae
Timestamp: 1765804665 Timestamp [UTC]: 2025-12-15 13:17:45 Age [y:d:h:m:s]: 00:342:07:16:20
Block: 1434159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249991 RingCT/type: yes/0
Extra: 013fefe6d7a8ed74dbbfc33b49d227357cb7e64349039710701e4bc2222400e3ae021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1dc23df67a26001bd2c569b69138444fced437fb1532558e20b521539b9a608b 0.000600000000 1922948 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": 1434169, "vin": [ { "gen": { "height": 1434159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dc23df67a26001bd2c569b69138444fced437fb1532558e20b521539b9a608b" } } ], "extra": [ 1, 63, 239, 230, 215, 168, 237, 116, 219, 191, 195, 59, 73, 210, 39, 53, 124, 183, 230, 67, 73, 3, 151, 16, 112, 30, 75, 194, 34, 36, 0, 227, 174, 2, 17, 0, 0, 0, 2, 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: