Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69a66aae52bd674707bbc9b74ad7980cf7c2ca261d45dcc98c547b2419ddb641

Tx prefix hash: 629f2e61a99547460b338cc494bc866b7a36b0a83887dc6cf642eb6c651ffd00
Tx public key: d34a8666cc768d28acc76c59c4aad31acbe3f90b07f3547bb3deca4cb1893218
Timestamp: 1772569015 Timestamp [UTC]: 2026-03-03 20:16:55 Age [y:d:h:m:s]: 00:261:18:55:42
Block: 1490009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192770 RingCT/type: yes/0
Extra: 01d34a8666cc768d28acc76c59c4aad31acbe3f90b07f3547bb3deca4cb1893218021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0dcb8025e6659eb1126eca1c62f5384b26613d7d5da1a6a49e5f1a88a3f42291 0.000600000000 1979509 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": 1490019, "vin": [ { "gen": { "height": 1490009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dcb8025e6659eb1126eca1c62f5384b26613d7d5da1a6a49e5f1a88a3f42291" } } ], "extra": [ 1, 211, 74, 134, 102, 204, 118, 141, 40, 172, 199, 108, 89, 196, 170, 211, 26, 203, 227, 249, 11, 7, 243, 84, 123, 179, 222, 202, 76, 177, 137, 50, 24, 2, 17, 0, 0, 0, 5, 241, 136, 200, 168, 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: