Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbfa8933fba9f1d9466035bb814fda894b74c49d3bae78efe837128aabfdcf75

Tx prefix hash: 99126644687271847e7f9cc16763fcc3e4c2be948bdc753366f8fe4fa7cf16c0
Tx public key: 1d64dd94de978d52ddfb62b628ac22791b7c9e2e3dc6a2052facaa74acc8df6b
Timestamp: 1638063583 Timestamp [UTC]: 2021-11-28 01:39:43 Age [y:d:h:m:s]: 04:358:02:35:33
Block: 383632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1298756 RingCT/type: yes/0
Extra: 011d64dd94de978d52ddfb62b628ac22791b7c9e2e3dc6a2052facaa74acc8df6b021100000002379224c2000000000000000000

1 output(s) for total of 0.032875192627 xmr

stealth address amount amount idx tag
00: c3350d722cb38c25da567014985dc95864945237799b00c53dea345d0acd4181 0.032875192627 774481 of 0 -

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": 383642, "vin": [ { "gen": { "height": 383632 } } ], "vout": [ { "amount": 32875192627, "target": { "key": "c3350d722cb38c25da567014985dc95864945237799b00c53dea345d0acd4181" } } ], "extra": [ 1, 29, 100, 221, 148, 222, 151, 141, 82, 221, 251, 98, 182, 40, 172, 34, 121, 27, 124, 158, 46, 61, 198, 162, 5, 47, 172, 170, 116, 172, 200, 223, 107, 2, 17, 0, 0, 0, 2, 55, 146, 36, 194, 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: