Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65945a7e5877ff69ec9307a023fe8d7de93aae6a6d8f036c0dff9c27cf64c67c

Tx prefix hash: 356e96e5e32816d4395b9e9bd535a64c3fcc2220b0da181959ed3f14a4e84541
Tx public key: 43310ebdf97d81f6b6956f80e059b32517e5f2312e19848ea2462f54ab8cfbb8
Timestamp: 1750829223 Timestamp [UTC]: 2025-06-25 05:27:03 Age [y:d:h:m:s]: 01:147:12:55:32
Block: 1312313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369752 RingCT/type: yes/0
Extra: 0143310ebdf97d81f6b6956f80e059b32517e5f2312e19848ea2462f54ab8cfbb8021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a8000262e97e84c9e4d299811afc294d3d2952a6721a885037d0a684bb0d08b 0.000600000000 1799946 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": 1312323, "vin": [ { "gen": { "height": 1312313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a8000262e97e84c9e4d299811afc294d3d2952a6721a885037d0a684bb0d08b" } } ], "extra": [ 1, 67, 49, 14, 189, 249, 125, 129, 246, 182, 149, 111, 128, 224, 89, 179, 37, 23, 229, 242, 49, 46, 25, 132, 142, 162, 70, 47, 84, 171, 140, 251, 184, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: