Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52afc200a74eedd730573e2fb65bab6715fa5ad03ee4200cb27bff352fd8e8be

Tx prefix hash: 749ee1cc0ac7f8107a4e760920f94edd4f747d397b5f2f63787ffead993e7b2a
Tx public key: edc018c882a77c37faffa239316888048d21912888d7de6b8db0ceb5ba1b6f00
Timestamp: 1775126133 Timestamp [UTC]: 2026-04-02 10:35:33 Age [y:d:h:m:s]: 00:231:16:14:50
Block: 1511167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171178 RingCT/type: yes/0
Extra: 01edc018c882a77c37faffa239316888048d21912888d7de6b8db0ceb5ba1b6f0002110000000aee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 11d5d6c5e5915086eb37966706bed3e050dc9dcb25e63e8a857f9772849401d0 0.000600000000 2000957 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": 1511177, "vin": [ { "gen": { "height": 1511167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11d5d6c5e5915086eb37966706bed3e050dc9dcb25e63e8a857f9772849401d0" } } ], "extra": [ 1, 237, 192, 24, 200, 130, 167, 124, 55, 250, 255, 162, 57, 49, 104, 136, 4, 141, 33, 145, 40, 136, 215, 222, 107, 141, 176, 206, 181, 186, 27, 111, 0, 2, 17, 0, 0, 0, 10, 238, 75, 113, 129, 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: