Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6e52479aa1c0aecfb8b17b449962fe95b9ab05928b36e9b77f4bfb0a1b41ec

Tx prefix hash: d2fde451ad7e68a690b7e2deab2205321c39d648d826fa227a2aab7d0a337b42
Tx public key: f95f4bd43aa649e6738e24f1b7d611f4c8dd186d8062943fdb9a720039ee4247
Timestamp: 1774520112 Timestamp [UTC]: 2026-03-26 10:15:12 Age [y:d:h:m:s]: 00:236:07:32:49
Block: 1506148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174390 RingCT/type: yes/0
Extra: 01f95f4bd43aa649e6738e24f1b7d611f4c8dd186d8062943fdb9a720039ee424702110000000de4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 86320338d3adf8e739a9d893e08a348dffaadae41cf1873e769f6fe80e2dcb0d 0.000600000000 1995892 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": 1506158, "vin": [ { "gen": { "height": 1506148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86320338d3adf8e739a9d893e08a348dffaadae41cf1873e769f6fe80e2dcb0d" } } ], "extra": [ 1, 249, 95, 75, 212, 58, 166, 73, 230, 115, 142, 36, 241, 183, 214, 17, 244, 200, 221, 24, 109, 128, 98, 148, 63, 219, 154, 114, 0, 57, 238, 66, 71, 2, 17, 0, 0, 0, 13, 228, 245, 25, 63, 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: