Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cc01a87684617fd4276dc0f5e5f4b60fda276713acb54764bfa15672e73a031

Tx prefix hash: b831470636bd110f44ad9fa163aab1ef45697ae9a20d5cf4edec610b7e562e28
Tx public key: bb600750b56585b8cc1366c19769bd77d534f3329da22cfe7f45566aa0c16b78
Timestamp: 1747168228 Timestamp [UTC]: 2025-05-13 20:30:28 Age [y:d:h:m:s]: 01:098:19:25:15
Block: 1282265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335313 RingCT/type: yes/0
Extra: 01bb600750b56585b8cc1366c19769bd77d534f3329da22cfe7f45566aa0c16b780211000000071f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9b67d771b2c1d5bba0b3b38b2b68343459dd6eae7b50e3ddf4d6128d74fed8cc 0.000600000000 1769672 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": 1282275, "vin": [ { "gen": { "height": 1282265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b67d771b2c1d5bba0b3b38b2b68343459dd6eae7b50e3ddf4d6128d74fed8cc" } } ], "extra": [ 1, 187, 96, 7, 80, 181, 101, 133, 184, 204, 19, 102, 193, 151, 105, 189, 119, 213, 52, 243, 50, 157, 162, 44, 254, 127, 69, 86, 106, 160, 193, 107, 120, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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: