Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8029fa1c0f0c8dbb2602372452ebd77065c846e16fe8b6824a9b6be0d8724123

Tx prefix hash: 29c01562061dccc771c7c7bd4ef292301d41691f0acfd85fb5c82d89b0c5b6ca
Tx public key: 72245b11e26a5f681b1f39acf894223312a9b3698f8df3ec28f34d3228318bf0
Timestamp: 1759429202 Timestamp [UTC]: 2025-10-02 18:20:02 Age [y:d:h:m:s]: 01:044:05:06:21
Block: 1381321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297918 RingCT/type: yes/0
Extra: 0172245b11e26a5f681b1f39acf894223312a9b3698f8df3ec28f34d3228318bf0021100000001a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 813c3d8fe5c32a1e8984f158b13c62b55ad6776fee3f1907060c312eb08dacf3 0.000600000000 1869440 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": 1381331, "vin": [ { "gen": { "height": 1381321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "813c3d8fe5c32a1e8984f158b13c62b55ad6776fee3f1907060c312eb08dacf3" } } ], "extra": [ 1, 114, 36, 91, 17, 226, 106, 95, 104, 27, 31, 57, 172, 248, 148, 34, 51, 18, 169, 179, 105, 143, 141, 243, 236, 40, 243, 77, 50, 40, 49, 139, 240, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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: