Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba297bde5c1b6155f180aa6337f63ecf792fab96e20c504a0ba52efe925b8db2

Tx prefix hash: 5f8d6c95d244a05468b8704ecb252abd4e7ee27b98f18bd8283e21618c6bfd5a
Tx public key: 33fdbe334f85019b1f4c9366b50d5dc30268b0e234f4e1dd179b169283f2966d
Timestamp: 1745632416 Timestamp [UTC]: 2025-04-26 01:53:36 Age [y:d:h:m:s]: 01:017:10:45:26
Block: 1269529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263314 RingCT/type: yes/0
Extra: 0133fdbe334f85019b1f4c9366b50d5dc30268b0e234f4e1dd179b169283f2966d0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 76930e10b4f61199816b7b9da36a92e8b3c4d1d766fdfcad06131a98744352ab 0.000600000000 1756768 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": 1269539, "vin": [ { "gen": { "height": 1269529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76930e10b4f61199816b7b9da36a92e8b3c4d1d766fdfcad06131a98744352ab" } } ], "extra": [ 1, 51, 253, 190, 51, 79, 133, 1, 155, 31, 76, 147, 102, 181, 13, 93, 195, 2, 104, 176, 226, 52, 244, 225, 221, 23, 155, 22, 146, 131, 242, 150, 109, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: